From: John Max Skaller <skaller@ozemail.com.au>
To: Luc Maranget <Luc.Maranget@inria.fr>
Cc: Brian Rogoff <bpr@best.com>, caml-list@inria.fr
Subject: Re: [Caml-list] ocaml and named constants
Date: Fri, 01 Jun 2001 11:45:56 +1000 [thread overview]
Message-ID: <3B16F3D4.74E326E0@ozemail.com.au> (raw)
In-Reply-To: <200105310922.LAA0000007458@beaune.inria.fr>
Luc Maranget wrote:
> But I have another remark as far a ``manifest constants'' are the issue, Polymorphic
> variants seem to do the job.
>
> After all, provided you do not care much about the actual value of Foo)
> you can write :
>
> match x with
> | `Foo -> ...
> | `Bar -> ...
> | _ -> ...
In the 'real world' the constants are often integers or strings
whose values are dictated by standards, and this technique
requires providing two functions to map the value to and
from variants.
Sometimes this is OK. Sometimes, it is a problem: for example
the library Posix support is lacking all the error codes
and socket options available on some platforms,
and there is no workaround (other than magic).
--
John (Max) Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850
checkout Vyper http://Vyper.sourceforge.net
download Interscript http://Interscript.sourceforge.net
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
prev parent reply other threads:[~2001-06-01 17:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 17:06 David Fox
2001-05-28 12:32 ` Xavier Leroy
2001-05-29 1:07 ` John Max Skaller
2001-05-29 12:12 ` Andreas Rossberg
2001-05-29 17:16 ` John Max Skaller
[not found] ` <skaller@ozemail.com.au>
2001-05-30 9:46 ` Wolfgang Lux
2001-05-29 13:50 ` Luc Maranget
2001-05-30 16:50 ` Brian Rogoff
2001-05-31 9:22 ` Luc Maranget
2001-05-31 16:34 ` Brian Rogoff
2001-06-01 4:39 ` David Fox
2001-06-01 1:45 ` John Max Skaller [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=3B16F3D4.74E326E0@ozemail.com.au \
--to=skaller@ozemail.com.au \
--cc=Luc.Maranget@inria.fr \
--cc=bpr@best.com \
--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