From: Chris Hecker <checker@d6.com>
To: William Lovas <wlovas@stwing.upenn.edu>, caml-list@inria.fr
Subject: Re: [Caml-list] Design advice
Date: Sat, 28 Sep 2002 15:46:03 -0700 [thread overview]
Message-ID: <4.3.2.7.2.20020928154107.03ac9a00@mail.d6.com> (raw)
In-Reply-To: <20020928190216.GA9876@force.stwing.upenn.edu>
> 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.
As I mentioned in my mail,
let suit_to_int = function
| Spades -> 0
| Hearts -> 1
| Diamonds -> 1
| Clubs -> 3
is a bug that the compiler can't find. That's why I said it was a
tradeoff. Also, having to type the constructors twice in the mli and the
ml is already a huge pain the ass for maintenance and refactoring in my
opinion, and having to do it a third time is completely lame. But yes,
magic is magic, so that's why I didn't say it was absolutely the right
thing. In reality, a ton of C code depends on this and it is documented to
work like this in the manual, so it's probably safe, but I don't like
fencing in the compiler folks any more than necessary. Hence, "choose your
poison".
Chris
-------------------
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 22:55 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
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 [this message]
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=4.3.2.7.2.20020928154107.03ac9a00@mail.d6.com \
--to=checker@d6.com \
--cc=caml-list@inria.fr \
--cc=wlovas@stwing.upenn.edu \
/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).