From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: mattias.waldau@abc.se, caml-list@inria.fr
Subject: Re: Same label in different types, how do people solve this?
Date: Fri, 8 Dec 2000 10:31:25 +0100 [thread overview]
Message-ID: <20001208103125.A556@lambda.u-strasbg.fr> (raw)
In-Reply-To: <20001208102229N.garrigue@kurims.kyoto-u.ac.jp>; from garrigue@kurims.kyoto-u.ac.jp on Fri, Dec 08, 2000 at 10:22:29AM +0900
On Fri, Dec 08, 2000 at 10:22:29AM +0900, Jacques Garrigue wrote:
> From: "Mattias Waldau" <mattias.waldau@abc.se>
>
> > In Ocaml, you cannot have the same label in different types, see the example
> > below where
> > point_2d hides point_3d.
> >
> > How do people normally code around this restriction? One solution is using
> > objects, but what other solutions are there? Can 'Polymorphic variants'
> > solve this?
>
> There are various ways. The most common is to differentiate label
> names (i.e. use x_3d and x_2d instead of x). Another more subtle one
> is to put the definitions in deifferent modules (Point2d and Point3d)
> so that you can specify exactly which label you want (Point2d.x or
> Point3d.x).
>
> The last solution might be nicer if we had a
> let open Module in
> construct (would require 10 lines in the compiler)
Is this not already possible ? i read about something similar in the docs
somewhere ...
Another idea would be to add some construct to use something like :
type p3d = { x:float;y:float;z:float }
type p2d = { x:float;y:float }
and then be able to do :
{p3d.x=10.;p3d.y=20.;p3d.z=30.}
and
{p2d.x=0; p2d.y=5}
Would this be difficult to do ?
Friendly,
Sven Luther
next prev parent reply other threads:[~2000-12-08 9:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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-12 19:24 ` Functions must be explicitly typed, (was Same label in different types, how do people solve this?) Mattias Waldau
2000-12-13 0:51 ` John Max Skaller
2000-12-15 10:13 ` Andreas Rossberg
2000-12-15 12:50 ` Frank Atanassow
2000-12-14 18:42 ` Stefan Monnier
2000-12-15 12:47 ` Pierre Weis
2000-12-15 13:39 ` Mattias Waldau
2000-12-15 23:37 ` Brian Rogoff
2000-12-16 14:10 ` ROverloading John Max Skaller
2000-12-15 21:51 ` Same label in different types, how do people solve this? Bruce Hoult
2000-12-12 17:19 ` John Max Skaller
2000-12-10 14:57 Ohad Rodeh
2000-12-13 13:17 Dave Berry
2000-12-13 14:31 ` Mattias Waldau
2000-12-15 10:01 ` 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=20001208103125.A556@lambda.u-strasbg.fr \
--to=luther@dpt-info.u-strasbg.fr \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
--cc=mattias.waldau@abc.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).