caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Remi Vanicat <vanicat@labri.u-bordeaux.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] NaN-safe min and max
Date: Wed, 15 Oct 2003 19:03:36 +0200	[thread overview]
Message-ID: <87u16a77rr.dlv@wanadoo.fr> (raw)
In-Reply-To: <18220.141.155.88.179.1066229526.squirrel@minsky-primus.homeip.net> (Yaron Minsky's message of "Wed, 15 Oct 2003 10:52:06 -0400 (EDT)")

"Yaron Minsky" <yminsky@cs.cornell.edu> writes:

> Olivier Andrieu proposed the following code for doing a safe min/max. 
> Does anyone have any thoughts about this code snippet, and whether it is
> or is not a safe use of Obj.magic?
>
>  let min a b =
>     let o = Obj.repr a in
>     if Obj.is_block o && Obj.tag o = Obj.double_tag
>     then Obj.magic (fmin (Obj.magic a) (Obj.magic b))
>     else Pervasives.min a b

this one is unsafe : the fact that a is a block with a tag
Obj.double_tag doesn't proof that the same is true for b even if a and
b have the same type :

# let i1 = Lazy.lazy_from_val 0.0;;
val i1 : float Lazy.t = lazy 0.
# let o1 = Obj.repr i1;;
val o1 : Obj.t = <abstr>
# Obj.is_block o1;;
- : bool = true
# Obj.tag o1 = Obj.double_tag;;
- : bool = true
# let i2 = lazy 3;;
val i2 : int lazy_t = <lazy>
# let o2 = Obj.repr i2;;
val o2 : Obj.t = <abstr>
# Obj.is_block o2;;
- : bool = true
#  Obj.tag o2 = Obj.double_tag;;
- : bool = false

both i1 and i2 have the same type, but only the first one is a block of
tag Obj.double_tag. A verification have to be done for both argument.
-- 
Rémi Vanicat
remi.vanicat@laposte.net

-------------------
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:[~2003-10-15 17:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 14:52 Yaron Minsky
2003-10-15 17:03 ` Remi Vanicat [this message]
2003-10-15 18:59   ` Remi Vanicat
2003-10-16  1:13   ` Jacques Garrigue

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=87u16a77rr.dlv@wanadoo.fr \
    --to=vanicat@labri.u-bordeaux.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;
as well as URLs for NNTP newsgroup(s).