From: Richard Jones <rich@annexia.org>
To: Chris Conway <cconway@courant.nyu.edu>
Cc: "Daniel Bünzli" <daniel.buenzli@erratique.ch>,
caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Camlidl questions
Date: Sun, 28 Oct 2007 21:48:38 +0000 [thread overview]
Message-ID: <20071028214836.GA16097@furbychan.cocan.org> (raw)
In-Reply-To: <Pine.GSO.4.63.0710271920270.7109@access2.cims.nyu.edu>
On Sat, Oct 27, 2007 at 07:27:15PM -0400, Chris Conway wrote:
> I'm afraid I don't understand this position at all. With a few dozen,
> mostly obvious, annotations to the header files, I have covered 99% of the
> library's functionality, automatically generating several thousand lines
> of low-level boilerplate code. Leaving aside the possibility of known bugs
> in Camlidl that might never get fixed... why would I want to code this all
> by hand?
Sorry, I was somehow confusing camlidl & SWIG.
Rich.
--
Richard Jones
Red Hat
prev parent reply other threads:[~2007-10-28 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 20:36 Christopher L Conway
2007-10-27 8:43 ` [Caml-list] " Daniel Bünzli
2007-10-27 16:45 ` Richard Jones
2007-10-27 23:27 ` Chris Conway
2007-10-28 21:48 ` Richard Jones [this message]
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=20071028214836.GA16097@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=caml-list@yquem.inria.fr \
--cc=cconway@courant.nyu.edu \
--cc=daniel.buenzli@erratique.ch \
/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).