From: Brian Hurt <bhurt@janestcapital.com>
To: Till Varoquaux <till.varoquaux@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Operator overloading
Date: Fri, 09 Mar 2007 11:02:25 -0500 [thread overview]
Message-ID: <45F18511.9060904@janestcapital.com> (raw)
In-Reply-To: <9d3ec8300703081434r6e4987d0l5f737d873f65d9ee@mail.gmail.com>
Till Varoquaux wrote:
> Hum...
>
> Instead of proving once again Godwin's law we might want to use
> constructive criticism (even though I also tend to flame more than my
> share)...
No, actually, I was making a point. The fact that you don't like the
point I was making doesn't make it a flame. Disagreeing with you is not
an insult. Although I do find amusing the implication that bringing up
pointer arithmetic is the equivelent to calling someone a Nazi.
Spelling the point out explicitly for those who missed it: when
considering wether to add a feature to a language, you have to consider
*BOTH* the valid uses of that feature *AND* the probable ways the
feature will be misused and the problems it will cause. You don't get
to ignore the downsides. Because, if you do, then there's no real
reason why introducing pointer arithmetic into Ocaml is not a good idea.
Brian
next prev parent reply other threads:[~2007-03-09 16:02 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 20:02 Robert Fischer
2007-03-08 20:15 ` Michael Hicks
2007-03-08 20:50 ` Brian Hurt
2007-03-08 21:05 ` Tom
2007-03-08 21:31 ` Brian Hurt
2007-03-08 22:09 ` Michael Vanier
2007-03-08 22:34 ` Till Varoquaux
2007-03-09 16:02 ` Brian Hurt [this message]
2007-03-10 3:23 ` skaller
2007-03-08 22:14 ` Ian Zimmerman
2007-03-09 10:29 ` Jon Harrop
2007-03-09 16:28 ` Ian Zimmerman
2007-03-08 23:51 ` skaller
2007-03-09 7:23 ` Tom
2007-03-09 9:24 ` skaller
2007-03-09 9:32 ` Tom
2007-03-09 10:00 ` skaller
2007-03-09 10:14 ` Jon Harrop
2007-03-09 10:38 ` Jon Harrop
2007-03-09 10:20 ` Jon Harrop
2007-03-09 12:08 ` Andrej Bauer
2007-03-09 12:48 ` Jacques Carette
2007-03-09 13:24 ` Andreas Rossberg
2007-03-10 5:08 ` Daniel Andor
2007-03-10 5:33 ` David Thomas
-- strict thread matches above, loose matches on Subject: below --
2007-03-09 16:40 Robert Fischer
2007-03-09 17:25 ` Jon Harrop
2007-03-09 7:36 oleg
2007-03-09 11:09 ` [Caml-list] " skaller
2007-03-09 13:52 ` Andreas Rossberg
2007-03-09 15:07 ` skaller
2007-03-09 16:28 ` Andreas Rossberg
2007-03-10 3:13 ` skaller
2007-03-08 23:20 Robert Fischer
2007-03-09 10:31 ` Jon Harrop
2007-03-08 14:41 [Caml-list] F# Robert Fischer
2007-03-08 17:30 ` Roland Zumkeller
2007-03-08 17:54 ` Brian Hurt
2007-03-08 19:40 ` [Caml-list] Operator overloading Jon Harrop
2007-03-08 20:44 ` Brian Hurt
2007-03-08 22:24 ` Fernando Alegre
2002-04-15 17:05 [Caml-list] operator overloading Issac Trotts
2002-04-14 4:15 Issac Trotts
2002-04-13 8:43 forsyth
2002-04-13 5:26 Issac Trotts
2002-04-13 1:32 Gurr, David (MED, self)
2002-04-12 19:08 Issac Trotts
2002-04-13 8:48 ` William Chesters
2002-04-13 13:58 ` Brian Rogoff
2002-04-13 15:31 ` William Chesters
2002-04-14 3:10 ` Brian Rogoff
2002-04-13 9:00 ` Daniel de Rauglaudre
2002-04-13 21:35 ` Johan Georg Granström
2002-04-14 1:50 ` Jacques Garrigue
2002-04-15 16:22 ` Jun P.FURUSE
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=45F18511.9060904@janestcapital.com \
--to=bhurt@janestcapital.com \
--cc=caml-list@yquem.inria.fr \
--cc=till.varoquaux@gmail.com \
/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).