caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jørgen Hermanrud Fjeld" <jhf@hex.no>
To: ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Understanding why Ocaml doesn't support operator overloading.
Date: Thu, 28 Nov 2002 22:27:14 +0100	[thread overview]
Message-ID: <200211282227.18402.jhf@hex.no> (raw)
In-Reply-To: <200211282202.44717.jhf@hex.no>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi again.
Now I found a previous thread about this
"http://caml.inria.fr/archives/200104/threads.html#00028"
I still don't understand why overloading isn't doable, (not only operator 
overloading)
And I wondered if any projects work on this?

On torsdag 28 november 2002, 22:02, Jørgen Hermanrud Fjeld wrote:
> Hi.
> Some time ago, when looking at Ocaml for the first time, I got baffled by
> the lack of operator overloading. I am still wondering why this is the
> case. Could someone please point me to more information about this?
>
> I remember reading something about operator overloading and type inference
> beeing hard to combine. A little googleing brought me, amongst many things,
> what seems to be a paper about the subject:
> "http://doi.acm.org/10.1145/581478.581495"
> (No I haven't read the paper yet, but it seemed ontopic)

- -- 
Sincerely | Homepage:
Jørgen    | http://www.hex.no/jhf
          | Public GPG key:
          | http://www.hex.no/jhf/key.txt

There are three schools of magic.  One:  State a tautology, then ring the
changes on its corollaries; that's philosophy.  Two:  Record many facts.
Try to find a pattern.  Then make a wrong guess at the next fact; that's
science.  Three:  Be aware that you live in a malevolent Universe controlled
by Murphy's Law, sometimes offset by Brewster's Factor; that's engineering.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE95ooy9jvTqPy5VsoRAsRCAJ9K3uuH2nK55WTFn4cRoK4NwfhpSQCeJEca
woLJurkjCSQqYi3k751obfo=
=EKLa
-----END PGP SIGNATURE-----

-------------------
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


  reply	other threads:[~2002-11-28 21:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-28 21:02 Jørgen Hermanrud Fjeld
2002-11-28 21:27 ` Jørgen Hermanrud Fjeld [this message]
2002-11-29 15:26 ` Xavier Leroy
2002-11-29 15:42   ` Christophe Raffalli
2002-11-29 16:52   ` Nicolas Cannasse
2002-11-29 17:26     ` Michal Moskal
2002-11-30  0:00       ` Mike Lin
2002-11-30 10:24         ` Michal Moskal
2002-11-30 23:06           ` Mike Lin
2002-11-30 21:41         ` William Lovas
2002-12-01 17:30           ` Pierre Weis
2002-12-01 23:41             ` William Lovas
2002-12-02  9:52               ` Remi VANICAT
2002-11-30 21:47         ` Pierre Weis
2002-12-01  7:40           ` Christophe Raffalli
2002-11-30 21:36       ` Pierre Weis
2002-11-30 21:33     ` Pierre Weis

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=200211282227.18402.jhf@hex.no \
    --to=jhf@hex.no \
    --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).