> 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