caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: art yerkes <ayerkes@speakeasy.net>
To: "HENRIKSON, JEFFREY" <JEFHEN@SAFECO.com>
Cc: micha-1@fantasymail.de, caml-list@inria.fr
Subject: Re: [Caml-list] swig like library...
Date: Sat, 24 Apr 2004 14:16:45 -0500	[thread overview]
Message-ID: <20040424141645.35c88843.ayerkes@speakeasy.net> (raw)
In-Reply-To: <9410EC84C0872141B27A2726613EF45D02A52D16@psmrdcex01.psm.pin.safeco.com>

On Fri, 23 Apr 2004 08:48:14 -0700
"HENRIKSON, JEFFREY" <JEFHEN@SAFECO.com> wrote:

> It attempts to be a more well behaved SWIG.  To my knowledge, I started
> the first attempt at a SWIG library.  I got frustrated with the
> infrastructure and quit.  Since then there have been at least 2 other
> attempts for ocaml swig support and recently I noticed there an official
> "ocaml swig".  Anyway, you can read about my complaints and my
> alternatives.

I chose to throw in with the SWIG project mainly because I had a C++
component library and no way of automatically wrapping it (About 200
classes, 800 methods).  I did not want to produce another wrapper
generator that takes a non-C++ input, nor do the wrapping by hand.

SWIG does have infrastructure problems.  It's really meant for generating
wrappers for typeless languages.  My first attempt at the SWIG module was
not general enough, which is why I took the approach of making the SWIG
output treat ocaml as a scripting language, too.  As far as I know, it's
the only project out there with as well developed a C++ reader (It
processes most C++ headers unmodified), and I'd recommend using it's s-exp
or xml output as a foundation for further work on wrapping, even if you
use nothing else from it.  That part has been tuned through experience,
and lots of the decisions that need to be taken are not covered by the C++
standard.

If others are interested in the module, I'm always willing to listen to
suggestions and take patches.
-- 
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


  reply	other threads:[~2004-04-24 19:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 15:48 HENRIKSON, JEFFREY
2004-04-24 19:16 ` art yerkes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-23 14:36 Michael
2004-04-23 15:07 ` Richard Jones
2004-04-23 15:47 ` Kenneth Knowles
2004-04-24  1:50 ` skaller
2004-04-24 17:12   ` Brandon J. Van Every
2004-04-24 20:11     ` skaller
2004-04-25  1:24       ` art yerkes
2004-04-25  2:56         ` skaller
2004-04-25  9:11         ` Yamagata Yoriyuki
2004-04-25 10:30           ` skaller
2004-04-26 15:17           ` art yerkes
2004-05-17 17:03             ` Yamagata Yoriyuki

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=20040424141645.35c88843.ayerkes@speakeasy.net \
    --to=ayerkes@speakeasy.net \
    --cc=JEFHEN@SAFECO.com \
    --cc=caml-list@inria.fr \
    --cc=micha-1@fantasymail.de \
    /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;
as well as URLs for NNTP newsgroup(s).