From: oliver <oliver@first.in-berlin.de>
To: David House <dhouse@janestreet.com>
Cc: "Gabriel Scherer" <gabriel.scherer@gmail.com>,
"Matej Košík" <5764c029b688c1c0d24a2e97cd764f@gmail.com>,
caml-list@inria.fr
Subject: Re: [Caml-list] syntactic detail
Date: Wed, 8 Feb 2012 17:30:08 +0100 [thread overview]
Message-ID: <20120208163007.GB4920@siouxsie> (raw)
In-Reply-To: <4F328BCF.9030902@janestreet.com>
On Wed, Feb 08, 2012 at 02:50:55PM +0000, David House wrote:
> On 02/08/2012 02:39 PM, Gabriel Scherer wrote:
> >People. Please. Tell me you are *not* arguing over underscores in
> >numeric literals !
>
> This is not totally academic. I have come across the exact bug I
> describe. It was painful.
[...]
Let me guess where the problem might be came from:
When i think of code that uses a value
1_000_000
and you want to change it to a value ten times higher,
it should be changed to
10_000_000
Coming from notation that does NOT allow "_" in tzhe numbers,
it could be done by just adding one "0" at the end of the value:
1000000
becomes
10000000
^
with the "0" added at the end.
But also correct ("more correct" would be:
1000000
becomes
10000000
^
"0" added at the millions.
"Just add one "0" at the end"
Is the edit-habit, which works fine.
But when allowing "_" inside numbers,
but people don't change the "wrong" editing behaviour,
then allowing the "_" at all means introducing a new kind
of possible errors.
This could be an argument to throw "_" at all,
because adding a "0" after the "1" instead of just
adding a "0" at the end is rarely used behaviour of editing,
and some people might call it "weird". ;-)
So this argument also could be used to disallow "_" at all.
But no, thats not what I want to argue for ;-)
OK, let's stop that discussion now.
If someone thinks the three-digit-distance-"_" is a feature that makes sense,
a feature wish could be added for OCaml. ;-)
Ciao,
Oliver
next prev parent reply other threads:[~2012-02-08 16:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 12:46 Matej Košík
2012-02-08 12:54 ` Gabriel Scherer
2012-02-08 13:09 ` David House
2012-02-08 13:39 ` oliver
2012-02-08 13:45 ` oliver
2012-02-08 13:46 ` David House
2012-02-08 13:58 ` oliver
2012-02-08 14:12 ` David House
2012-02-08 14:39 ` Gabriel Scherer
2012-02-08 14:50 ` David House
2012-02-08 15:19 ` Vincent Aravantinos
2012-02-10 8:39 ` Andrew
2012-02-08 16:30 ` oliver [this message]
2012-02-10 3:37 ` Jun Furuse
2012-02-08 16:21 ` oliver
2012-02-08 13:05 ` rixed
2012-02-09 9:05 ` Matej Košík
2012-02-09 10:56 ` Wojciech Meyer
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=20120208163007.GB4920@siouxsie \
--to=oliver@first.in-berlin.de \
--cc=5764c029b688c1c0d24a2e97cd764f@gmail.com \
--cc=caml-list@inria.fr \
--cc=dhouse@janestreet.com \
--cc=gabriel.scherer@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).