caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jeff Henrikson" <jehenrik@yahoo.com>
To: "Sven" <luther@dpt-info.u-strasbg.fr>
Cc: <caml-list@inria.fr>
Subject: RE: [Caml-list] Confusion about camlidl capabilities? other tools?
Date: Mon, 13 Aug 2001 20:26:10 -0400	[thread overview]
Message-ID: <001901c12457$b763a4c0$0b01a8c0@mit.edu> (raw)
In-Reply-To: <20010813225308.B23936@dpt-info.u-strasbg.fr>

> I started working some time ago on c2caml, which, altough maybe not
> what you need, was intented to generate ocaml stubs from C header
> code, particularly for parsing the gtk+ headers and generating
> appropriate bndings. It is really jus ta C parser for now, but if
> you want, you can look at it, it is availabel in the CDK, i think.

No, wrong way.  I want to publish a control implemented in caml to the outside world.  Parsing C is not involved.  Printing a bunch
of C is.

Note that this is easier than the reverse: C header files are underspecified and need a markup language (MIDL, SWIG) to make stub
generation well defined.  mli files on the other hand have everything you need to interface to C or something else.


Jeff Henrikson

> -----Original Message-----
> From: Sven [mailto:luther@dpt-info.u-strasbg.fr]
> Sent: Monday, August 13, 2001 4:53 PM
> To: Jeff Henrikson
> Subject: Re: [Caml-list] Confusion about camlidl capabilities? other
> tools?
>
>
> On Mon, Aug 13, 2001 at 03:26:46PM -0400, Jeff Henrikson wrote:
> > Hi,
> >
> > Reading the documentation of camlidl, it says that caml objects can be exported for use in C/C++ programs.  Looking at
> the source
> > code, the support for this looks minimal.  I see the camlidldll script, which is just a shell script that links a caml
> program with
> > some executable code.  If this is some sort of automatic dispatch interface generator, this is not what I want.  I want real C
> > header files from just plain unannotated mli.  Preferably a system with ability to map variants into C struct/unions
> coupled with
> > utility functions.  I'm not sure which other advanced ocaml datatypes I need beyond variants and the basic ints,
> strings, arrays
> > and etc.
> >
> > Has anybody done something like this?  I ripped out the ocaml parser and started playing with it to build a tool, but
> I don't want
> > to be reinventing the wheel.  While I'm at it, I will probably try to export stubs at least these styles: COM,
> GTK-style C objects,
> > and SWIG-ready header files for inclusion in Python or TCL or whatever some unenlightened person would want to use.
>
> I started working some time ago on c2caml, which, altough maybe not what you
> need, was intented to generate ocaml stubs from C header code, particularly
> for parsing the gtk+ headers and generating appropriate bndings. It is really
> jus ta C parser for now, but if you want, you can look at it, it is availabel
> in the CDK, i think.
>
> Friendly,
>
> Sven Luther
>

-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


       reply	other threads:[~2001-08-14  0:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010813225308.B23936@dpt-info.u-strasbg.fr>
2001-08-14  0:26 ` Jeff Henrikson [this message]
2001-08-13 19:26 Jeff Henrikson
2001-08-14  7:51 ` Xavier Leroy

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='001901c12457$b763a4c0$0b01a8c0@mit.edu' \
    --to=jehenrik@yahoo.com \
    --cc=caml-list@inria.fr \
    --cc=luther@dpt-info.u-strasbg.fr \
    /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).