Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Ian Zimmerman <itz@speakeasy.org>
To: caml-list@inria.fr (OCAML)
Subject: [Caml-list] CAMLparam and CAMLreturn
Date: 15 Jan 2002 14:24:16 -0800	[thread overview]
Message-ID: <86r8oruub3.fsf@speakeasy.org> (raw)


The documentation for custom blocks (section 17.9.1) says that the
compare, hash, and serialize custom block functions must use CAMLparam
for their arguments and CAMLreturn for their return values.  But
elsewhere it says that this is only a requirement for C functions that
can cause heap activity (by allocating blocks), and that certainly
makes better sense.

Is this because of multithreading?  Or what is the straight dope?

-- 
Ian Zimmerman, Oakland, California, U.S.A.
GPG: 433BA087  9C0F 194F 203A 63F7 B1B8  6E5A 8CA3 27DB 433B A087
In his own soul a man bears the source
from which he draws all his sorrows and his joys.
Sophocles.
-------------------
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:[~2002-01-15 22:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=86r8oruub3.fsf@speakeasy.org \
    --to=itz@speakeasy.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