From: ronniec95@lineone.net
To: "Richard Jones" <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] CamlDL/Abstract pointers problem
Date: Thu, 29 Jan 2004 15:52:10 +0000 [thread overview]
Message-ID: <40169E8D00006A9F@mk-cpfrontend-1.mail.uk.tiscali.com> (raw)
In-Reply-To: <20040129150209.GB30750@redhat.com>
I understand that bit ok. But what I wanted to know is why CAMLIDL was not
doing this for me... as I said in my original email, I'm quite happy handwriting
all this stuff (Abstract_tag/Custom_tag all ok for me )- it works fine,
but is quite dull!
I specifically wanted to know what it is about camlidl which stops it generating
the correct code for this.
Ronnie
>-- Original Message --
>Date: Thu, 29 Jan 2004 15:02:09 +0000
>To: ronniec95@lineone.net
>Cc: caml-list@inria.fr
>Subject: Re: [Caml-list] CamlDL/Abstract pointers problem
>From: Richard Jones <rich@annexia.org>
>
>
>On Thu, Jan 29, 2004 at 01:06:39PM +0000, ronniec95@lineone.net wrote:
> All I want to do is just give Ocaml a pointer to something I've created
> in C and pass it back to other C functions later; don't want it to do
anything
> with it (including mo
>ing it around the ocaml heap).\
It's my understanding that you can't just pass a pointer back to OCaml
and cast it to a value. OCaml will think that the pointer points to
an OCaml heap object, and hence try to examine / move / delete it in
the g
>rbage collector. Instead you need to do one of two things:
either set the bottom bit to 1, in which case OCaml will treat it as a
plain integer, or else wrap it up in a box, as in the code below. The
Abstract_tag tells the garbage collector not to
>look inside the box.
static value
Val_voidptr (void *ptr)
{
CAMLparam0 ();
CAMLlocal1 (rv);
rv = alloc (1, Abstract_tag);
Field(rv, 0) = (value) ptr;
CAMLreturn (rv);
}
#define Voidptr_val(type,rv) ((type *) Field ((rv), 0))
>ou need to call Val_voidptr to wrap up your C void* pointer into an
OCaml box, and Voidptr_val to unwrap and get your pointer back again.
In any case you need to also add lots of calls to Gc.full_major () to
your code, which will trigger an early
>ore dump if there is some
memory corruption.
Rich.
--
Richard Jones. http://www.annexia.org/ http://www.j-london.com/
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
If I have not seen as far as others, it is beca
>se I have been
standing in the footprints of giants. -- from Usenet
-------------------
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
next prev parent reply other threads:[~2004-01-29 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 13:06 ronniec95
2004-01-29 15:02 ` Richard Jones
2004-01-29 15:52 ` ronniec95 [this message]
2004-01-29 16:32 ` art yerkes
2004-01-29 19:04 ` skaller
2004-01-29 19:26 ` Richard Jones
2004-01-29 19:55 ` Alain.Frisch
2004-01-29 20:24 ` Richard Jones
2004-01-29 23:07 ` David Brown
2004-01-30 0:20 ` Jacques Garrigue
2004-01-30 7:04 ` Brian Hurt
2004-01-30 15:36 ` Jacques Garrigue
2004-01-30 16:52 ` Brian Hurt
2004-01-30 20:56 ` skaller
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=40169E8D00006A9F@mk-cpfrontend-1.mail.uk.tiscali.com \
--to=ronniec95@lineone.net \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
/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