From: Brian Rogoff <bpr@best.com>
To: Luc Maranget <Luc.Maranget@inria.fr>
Cc: John Max Skaller <skaller@ozemail.com.au>, caml-list@inria.fr
Subject: Re: [Caml-list] ocaml and named constants
Date: Wed, 30 May 2001 09:50:13 -0700 (PDT) [thread overview]
Message-ID: <Pine.BSF.4.21.0105300940580.19818-100000@shell5.ba.best.com> (raw)
In-Reply-To: <200105291350.PAA0000018491@beaune.inria.fr>
On Tue, 29 May 2001, Luc Maranget wrote:
> >
> > Is there any semantic reason why
> > one cannot use variables, or even expressions? Apart from
> > the obvious syntactic problem.
>
> Not that obvious, I think this would make pattern-matching look
> like even more complicated.
> It is good to stress on the fact that
> in match .. with p ->, p is a pattern
> 1. Some value ``whith holes''
> 2. Something we programmer and compiler know without any computation.
I read a paper on an SML extension to handle this named constant problem,
here at ftp://ftp.research.bell-labs.com/dist/smlnj/papers/92-tr-aitken.ps
Anyone know why this or some similar approach hasn't caught on? The CamlP4
approach isn't too bad, but this seems important enough to be in the core
language.
This is certainly on my "wish list" for future enhancements, since there
are so many cases where named constants are useful and the current
workarounds are a bit ugly.
-- Brian
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-05-30 16:50 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 [this message]
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
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.BSF.4.21.0105300940580.19818-100000@shell5.ba.best.com \
--to=bpr@best.com \
--cc=Luc.Maranget@inria.fr \
--cc=caml-list@inria.fr \
--cc=skaller@ozemail.com.au \
/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