From: Damien Doligez <damien.doligez@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Questions about the C interface
Date: Wed, 26 Feb 2003 17:49:43 +0100 [thread overview]
Message-ID: <4E293B08-49AA-11D7-9963-0003930FCE12@inria.fr> (raw)
In-Reply-To: <878ywkbs5j.fsf@student.uni-tuebingen.de>
On Thursday, February 13, 2003, at 07:39 AM, Falk Hueffner wrote:
> I would like to use C functions to manipulate small binary objects and
> Ocaml to manage these objects in data structures. So far, I used
> alloc_small(WORDS, Abstract_tag) to allocate them. However, that means
> I cannot put them into a Hashtbl, and I cannot compare them. Do I need
> "custom blocks" to achieve that?
Yes.
> I don't really need any fancy
> comparison or hash function, plain memcmp and hash would do. So I
> would like to save the overhead of one pointer per object and the more
> costly calling.
Unfortunately, we don't have a tag for uninterpreted binary data.
The closest we have is strings, but you'd still lose one word,
because of the final NUL byte.
> Also, I'm wondering when exactly I need CAMLparam/local.
If you want to know *exactly*, then the answer is incredibly
complex.
> I would think
> that if I don't allocate anything in the C function, I don't need to
> protect locals.
That's true.
> Also, I would
> think that values that are really ints don't need protection...
Also true.
> The manual doesn't mention that, though.
Taking advantage of all these exceptions is very error-prone, and we
don't want to encourage it.
> Finally, I wonder why the first parameter to alloc_custom (the ops
> block) is not a const pointer?
Because we don't believe in the const keyword. It's more trouble
than it's worth.
-- Damien
-------------------
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:[~2003-02-26 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 6:39 Falk Hueffner
2003-02-26 16:49 ` Damien Doligez [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=4E293B08-49AA-11D7-9963-0003930FCE12@inria.fr \
--to=damien.doligez@inria.fr \
--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