From: Robert Roessler <roessler@rftp.com>
To: "Sébastien Hinderer" <Sebastien.Hinderer@ens-lyon.org>
Cc: Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Should one use caml_ prefix in C code ?
Date: Sun, 27 Mar 2005 21:07:23 -0800 [thread overview]
Message-ID: <4247910B.9050702@rftp.com> (raw)
In-Reply-To: <20050328044327.GA2437@galois>
Sébastien Hinderer wrote:
> Among Caml header files is one called compatibility.h.
> This file defines macros allowing one to use, say, copy_string rather
> than caml_copy_string when writing stub functions.
> But what is the recommended style for writing stubs ?
> Should the caml_ prefix be used, or not ?
> The documentation does not seem to mention anything about that.
The "caml_" prefix was added in 3.08.0 to avoid name conflicts when
linking with other libraries. I believe the relevant entries in
compatibility.h are there so the Caml developers were not forced to
edit all of the sources... but you should use the new "official"
naming in code you write that needs to reference the affected C
globals. :)
Robert Roessler
roessler@rftp.com
http://www.rftp.com
prev parent reply other threads:[~2005-03-28 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 4:43 Sébastien Hinderer
2005-03-28 5:07 ` Robert Roessler [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=4247910B.9050702@rftp.com \
--to=roessler@rftp.com \
--cc=Sebastien.Hinderer@ens-lyon.org \
--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).