From: William Lovas <wlovas@stwing.upenn.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Design advice
Date: Sat, 28 Sep 2002 15:02:17 -0400 [thread overview]
Message-ID: <20020928190216.GA9876@force.stwing.upenn.edu> (raw)
In-Reply-To: <4.3.2.7.2.20020928033941.03b2eb10@mail.d6.com>
On Sat, Sep 28, 2002 at 03:55:43AM -0700, Chris Hecker wrote:
> >type, but now I have to convert this to an integer whenever I want to
> >use the player number as an index.
>
> type suit = Spades | Hearts | Diamonds | Clubs
>
> let suit_to_int (s : suit) =
> assert (Obj.is_int (Obj.repr s));
> ((Obj.magic s) : int)
>
> The assert will catch it if you add variables to one of the constructors
> and then call this. This uses magic, which is bad, but it alleviates you
> having to type the variant constructors again and possibly make an error in
> the assocation with the int, which is good. Pick your poison.
Wouldn't it be safer to just do something like:
let suit_to_int = function
| Spades -> 0
| Hearts -> 1
| Diamonds -> 2
| Clubs -> 3
? You only have to type it once, and if you change the constructors
around, it won't even compile. Plus it gives you control over which
int a suit corresponds to -- i doubt you can get any sort of guarantee
if you use Obj.magic.
William
-------------------
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:[~2002-09-28 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 16:47 Dan Schmidt
2002-09-28 10:48 ` John Prevost
2002-09-28 10:55 ` Chris Hecker
2002-09-28 19:02 ` William Lovas [this message]
2002-09-28 22:01 ` John Gerard Malecki
2002-09-28 23:03 ` Chris Hecker
2002-09-30 15:35 ` Kontra, Gergely
2002-09-28 22:46 ` Chris Hecker
2002-09-29 12:27 ` Lauri Alanko
2002-09-30 16:03 ` Alessandro Baretta
2002-10-01 11:37 ` Xavier Leroy
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=20020928190216.GA9876@force.stwing.upenn.edu \
--to=wlovas@stwing.upenn.edu \
--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).