From: "Gurr, David (MED, self)" <David.Gurr@med.ge.com>
To: "Kontra, Gergely" <kgergely@mlabdial.hit.bme.hu>
Cc: caml-list@inria.fr,
"Gurr David (MED Self) (E-mail)" <David.Gurr@med.ge.com>
Subject: RE: [Caml-list] Does this function exist?
Date: Wed, 18 Sep 2002 18:01:05 -0500 [thread overview]
Message-ID: <D4DBD8568F05D511A1C20002A55C008C09C2956A@uswaumsx03medge.med.ge.com> (raw)
> -----Original Message-----
> From: Kontra, Gergely [mailto:kgergely@mlabdial.hit.bme.hu]
> Sent: Tuesday, September 17, 2002 9:21 AM
> To: John Prevost
> Cc: Lukasz Lew; caml-list@inria.fr
> Subject: Re: [Caml-list] Does this function exist?
>
>
> >Doesn't matter--you still need type information.
>
> BTW allowing polymorphism doesn't solve the problem? Ocaml is strictly
> typed, so one can figure out it's parameter in compile-type, right?
> Or wrong?
Most ML languages do type erasure rather than
dictionary passing. Yeah, the compiler knows the type,
but you want the runtime to know the type. But the
runtime doesn't know much more than int,float,closure,
pointer to something with a constructor tag. Java's
reflection and C++ RTTI come at a price that is
considered wrong by designers who pick type erasure.
I am a fan of reflection but I agree with Ocaml's
choices. What you seem to want is IMHO something
that is right for debuggers and interactive toploops
but not other code, thus they not the other code should
pay the price. Read up on implementation of ML on
JVM or MSCLR for an alternative to the Ocaml choices.
-D
PS if you are really into this, you could implement
RTTI with preprocessing via camlp4 (?or MetaOcaml?).
> Gergo
>
> +-[Kontra, Gergely @ Budapest University of Technology and
> Economics]-+
> | Email: kgergely@mcl.hu, kgergely@turul.eet.bme.hu
> |
> | URL: turul.eet.bme.hu/~kgergely Mobile: (+36 20) 356
> 9656 |
> +-------"Olyan langesz vagyok, hogy poroltoval kellene
> jarnom!"-------+
> .
> Magyar php mirror es magyar php dokumentacio: http://hu.php.net
>
> -------------------
> To unsubscribe, mail caml-list-request@inria.fr Archives:
> http://caml.inria.fr
> Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ:
> http://caml.inria.fr/FAQ/
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2002-09-18 23:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 23:01 Gurr, David (MED, self) [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-18 23:01 Gurr, David (MED, self)
2002-09-09 17:56 Lukasz Lew
2002-09-09 19:34 ` John Prevost
2002-09-09 20:18 ` Lukasz Lew
2002-09-09 20:55 ` John Prevost
2002-09-09 20:59 ` Lukasz Lew
2002-09-17 16:21 ` Kontra, Gergely
2002-09-17 17:17 ` Florian Hars
2002-09-09 21:40 ` Yutaka OIWA
2002-09-09 23:10 ` Nicolas Cannasse
[not found] ` <Pine.LNX.4.44.0209092212360.21417-100000@zodiac.mimuw.edu. pl>
2002-09-09 22:05 ` Chris Hecker
2002-09-09 22:48 ` Remi VANICAT
2002-09-10 1:10 ` Daniel de Rauglaudre
2002-09-16 16:56 ` Kontra, Gergely
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=D4DBD8568F05D511A1C20002A55C008C09C2956A@uswaumsx03medge.med.ge.com \
--to=david.gurr@med.ge.com \
--cc=caml-list@inria.fr \
--cc=kgergely@mlabdial.hit.bme.hu \
/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