caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <xavier.leroy@inria.fr>
To: Warp <warplayer@free.fr>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Tuple copy
Date: Wed, 6 Mar 2002 11:54:36 +0100	[thread overview]
Message-ID: <20020306115436.A4830@pauillac.inria.fr> (raw)
In-Reply-To: <008c01c1c477$f2a9ef60$3000a8c0@warp>; from warplayer@free.fr on Tue, Mar 05, 2002 at 07:59:58PM +0100

> I got the following question : I have a type MSG wich is allocated using
> alloc_tuple(3) , and contains one Int and two Int32.
> Sometimes, the second Int32 is a C pointer, so I managed to garbage it by
> allocating sometimes MSG using alloc_tuple(4) and then storing a custom
> block in the fourth block (this custom block hold the C pointer, and will
> free() it when garbaged - the C pointer is also stored as an Int32 in the
> MSG to enable its access by C API ). So for the same type MSG, i'm mixing
> tuple of different sizes.
> 
> Does this can cause problems ?

It won't crash the program.  The GC "sees" the fourth field and
handles it correctly, while the Caml code never "sees" it (it trusts
the type declaration that says that the result is a triple).

However, primitives such as generic equality might return unexpected
results (but again they won't crash).  For instance, a 3-tuple MSG
will never be equal to a 4-tuple MSG, even though both agree on the
first 3 fields (and thus print identically under the toplevel, for
instance).

- Xavier Leroy
-------------------
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


      reply	other threads:[~2002-03-06 10:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05 18:59 Warp
2002-03-06 10:54 ` Xavier Leroy [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=20020306115436.A4830@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=warplayer@free.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).