From: art yerkes <ayerkes@speakeasy.net>
To: erayo@cs.bilkent.edu.tr
Cc: exa@kablonet.com.tr, gnu04@yahoo.com, caml-list@inria.fr
Subject: Re: [Caml-list] Interface between Ocaml and C++
Date: Tue, 22 Jun 2004 01:41:43 -0500 [thread overview]
Message-ID: <20040622014143.6e6870ab.ayerkes@speakeasy.net> (raw)
In-Reply-To: <200406212224.07538.exa@kablonet.com.tr>
On Mon, 21 Jun 2004 22:24:07 +0300
Eray Ozkural <exa@kablonet.com.tr> wrote:
> On Saturday 19 June 2004 10:29, art yerkes wrote:
> > The SWIG module for Ocaml has support for a few STL
> > types. If you use those interfaces as a guide, you
> > could add support for more if the automatic wrapping
> > doesn't suit.
> >
> > SWIG isn't perfect for everyone but some needs are
> > met very well, including using templates.
> >
> > Look at http://www.swig.org/
>
> How does it handle convert C++ templates to ocaml code, I wonder. I had a
> design in my mind, but it required quite a bit of monkeying around. What's
> their solution?
The current solution is to specify which specializations of a given template
will be needed, after which the specialized template classes are treated as
ordinary classes.
--
Hey, Adam Smith, keep your invisible hands to yourself!
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-06-22 6:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 4:56 Gu Nu
2004-06-19 7:29 ` art yerkes
2004-06-21 19:24 ` Eray Ozkural
2004-06-22 6:41 ` art yerkes [this message]
2004-06-22 11:14 ` Eray Ozkural
2004-06-22 13:36 ` art yerkes
2004-06-22 18:44 ` Eray Ozkural
2004-06-22 23:06 ` Brandon J. Van Every
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040622014143.6e6870ab.ayerkes@speakeasy.net \
--to=ayerkes@speakeasy.net \
--cc=caml-list@inria.fr \
--cc=erayo@cs.bilkent.edu.tr \
--cc=exa@kablonet.com.tr \
--cc=gnu04@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox