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