caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "FabienFleutot" <fleutotf@esiee.fr>
To: "Caml List" <caml-list@inria.fr>
Subject: Re: [Caml-list] a reckless proposal
Date: Wed, 25 Jul 2001 10:30:49 +0200	[thread overview]
Message-ID: <002b01c114e4$1bb52580$6ec809c0@fabien> (raw)
In-Reply-To: <20010724110817.A35216@caddr.com>

> The most frustrating feature of records, of course, is that each record
field
> name must be globally unique.
> [...]
> less confusing and
> more comfortable to C/C++/Java/Python programmers.

Some old K&R C compilers also need unique struct fields id. (That's probably
why the Un*x struct fields have unique prefixes).

This unique struct field id. in caml allows to easily guess a struct's type
in a pattern-matching; I'll write about GCaml without having read related
papers nor compiler sources, but wouldn't it be possible, with GCaml type
engine, to introduce the required polymorphism in non-unique struct field
name pattern matching?
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  parent reply	other threads:[~2001-07-25 21:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-24 18:08 Miles Egan
2001-07-24 19:44 ` Brian Rogoff
2001-07-24 21:02   ` Miles Egan
2001-07-25 15:15     ` Brian Rogoff
2001-07-26 15:27       ` Miles Egan
2001-07-26 15:47         ` Brian Rogoff
2001-07-26 16:01           ` Miles Egan
2001-07-26 21:19   ` John Max Skaller
2001-07-24 20:26 ` Sven
2001-07-24 20:51   ` Miles Egan
2001-07-25  8:30 ` FabienFleutot [this message]
2001-07-25  9:30 Dave Berry
2001-07-26 15:35 ` Miles Egan
2001-07-30 12:21   ` Bruce Hoult

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='002b01c114e4$1bb52580$6ec809c0@fabien' \
    --to=fleutotf@esiee.fr \
    --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).