From: Shishir Ramam <sramam@gmail.com>
To: caml list <caml-list@inria.fr>
Subject: Re: [Caml-list] CamlIdl possible issue
Date: Mon, 16 Aug 2004 16:04:46 -0700 [thread overview]
Message-ID: <83f5996804081616046fb7e120@mail.gmail.com> (raw)
In-Reply-To: <41212700.9070004@libertysurf.fr>
Matthieu,
Thanks for the quick response.
> If this problem appears not two often you can avoid it by adding your
> own ml2c and c2ml functions using the attributes ml2c and c2ml.
That is exactly what I have done.
Was wondering if there's any chance I can influence a change in the
design for this case.
regards,
-shishir
-------------------
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
prev parent reply other threads:[~2004-08-16 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 19:46 Shishir Ramam
2004-08-16 21:28 ` Matthieu Dubuget
2004-08-16 23:04 ` Shishir Ramam [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=83f5996804081616046fb7e120@mail.gmail.com \
--to=sramam@gmail.com \
--cc=caml-list@inria.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).