From: Hal Daume III <hdaume@ISI.EDU>
To: Oliver Bandel <oliver@first.in-berlin.de>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] generic data type -> int function
Date: Thu, 31 Mar 2005 06:33:54 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.44.0503310633170.715-100000@albini.isi.edu> (raw)
In-Reply-To: <20050330222944.GB443@first.in-berlin.de>
> > type etype = GPE | LOC | ORG | PER | NAE_e | BOS_e
> > type mtype = BAR | NAM | NOM | PRE | PRO | OTHER | NAE_m | BOS_m
> > type pairs = EM of etype*mtype | EE of etype*etype | MM of mtype*mtype
> > type pairs2 = EP of etype * pairs | MP of mtype * pairs
> >
> >
> > Corresponding output:
> >
> > let int_of_etype = function | GPE -> 0 | LOC -> 1 | ORG -> 2 | PER -> 3 | NAE_e -> 4 | BOS_e -> 5
> > let int_of_mtype = function | BAR -> 0 | NAM -> 1 | NOM -> 2 | PRE -> 3 | PRO -> 4 | OTHER -> 5 | NAE_m -> 6 | BOS_m -> 7
>
>
> ...ooops... GPE as well as BAR has the same output-value...
> ...so... if there is no problem with that kind of similar integers,
> why don't you use Kims solution?!
> Ut seemed to me that it has solved your problem, at least in this respect.
Because it cannot handle the 'type pairs' or 'type pairs2' above. The
enumerations are unique per type.
--
Hal Daume III | hdaume@isi.edu
"Arrest this man, he talks in maths." | www.isi.edu/~hdaume
next prev parent reply other threads:[~2005-03-31 14:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 16:38 Hal Daume III
2005-03-25 11:37 ` [Caml-list] " Jean-Christophe Filliatre
2005-03-30 3:26 ` Hal Daume III
2005-03-30 22:27 ` Oliver Bandel
2005-03-31 14:33 ` Hal Daume III
2005-03-31 17:01 ` Richard Jones
2005-03-31 18:04 ` Hal Daume III
2005-03-30 22:29 ` Oliver Bandel
2005-03-31 14:33 ` Hal Daume III [this message]
2005-03-25 19:15 ` Kim Nguyen
2005-03-29 7:29 ` Oliver Bandel
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=Pine.LNX.4.44.0503310633170.715-100000@albini.isi.edu \
--to=hdaume@isi.edu \
--cc=caml-list@yquem.inria.fr \
--cc=oliver@first.in-berlin.de \
/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).