From: John Max Skaller <skaller@ozemail.com.au>
To: Mattias Waldau <mattias.waldau@tacton.se>
Cc: Dave Berry <dave@kal.com>, Chris Hecker <checker@d6.com>,
Mattias Waldau <mattias.waldau@abc.se>,
Caml-List <caml-list@inria.fr>
Subject: Re: Same label in different types, how do people solve this?
Date: Fri, 15 Dec 2000 21:01:00 +1100 [thread overview]
Message-ID: <3A39EBDC.662801DF@ozemail.com.au> (raw)
In-Reply-To: <HDEEKOMJILGEIHIMAPCDAEPHDLAA.mattias.waldau@tacton.se>
Mattias Waldau wrote:
>
> My problems isn't the restriction as such. If I know about the restriction,
> I can code around it.
>
> The problem is that this particular restriction is very unusual, and
> therefor I need to be informed about this. Now it is in the faq, but why not
> put it into the error message "two fields in different types in the same
> file/module cannot have the same name."
It's not clear:
open A (* contains field x *)
open B (* contains field x *)
expr.x (* B.x *)
expr.A.x (* A.x *)
expr.B.x (* B.x *)
Possibly, it is the _usage_ 'expr.x' which should be flagged
as erroneous, which would suggest:
open List
open Array
..
map f []
map f [| |]
both applications ought to be in error (rather than just map f []).
This would break a LOT of code I'd imagine, even if it is
'better principled' than the current scheme, which might lead to
confusing messages.
--
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
next prev parent reply other threads:[~2000-12-15 12:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 13:17 Dave Berry
2000-12-13 14:31 ` Mattias Waldau
2000-12-15 10:01 ` John Max Skaller [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-10 14:57 Ohad Rodeh
2000-12-06 21:22 Mattias Waldau
2000-12-07 16:49 ` John Max Skaller
2000-12-07 18:34 ` Maxence Guesdon
2000-12-07 23:02 ` Gerd Stolpmann
2000-12-08 1:22 ` Jacques Garrigue
2000-12-08 9:31 ` Sven LUTHER
2000-12-08 9:36 ` Pierre Weis
2000-12-08 9:48 ` Sven LUTHER
2000-12-08 18:41 ` John Max Skaller
2000-12-08 9:40 ` Nicolas barnier
2000-12-08 16:36 ` Brian Rogoff
2000-12-11 17:19 ` Pierre Weis
2000-12-10 12:49 ` Mattias Waldau
2000-12-11 18:23 ` Chris Hecker
2000-12-11 19:17 ` Pierre Weis
2000-12-12 10:02 ` Sven LUTHER
2000-12-12 3:25 ` Chet Murthy
2000-12-12 17:43 ` John Max Skaller
2000-12-15 21:51 ` Bruce Hoult
2000-12-12 17:19 ` 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=3A39EBDC.662801DF@ozemail.com.au \
--to=skaller@ozemail.com.au \
--cc=caml-list@inria.fr \
--cc=checker@d6.com \
--cc=dave@kal.com \
--cc=mattias.waldau@abc.se \
--cc=mattias.waldau@tacton.se \
/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).