From: Stanislav Artemkin <artemkin@gmail.com>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Unary negation parsing
Date: Thu, 3 Dec 2015 14:02:50 +0400 [thread overview]
Message-ID: <CAL4yAN=b_ihMvvErgFkSV3tMMhTSJfMibuDDJKZ-S4_iUMbFcg@mail.gmail.com> (raw)
In-Reply-To: <1449089348.15053.10.camel@zotac>
[-- Attachment #1: Type: text/plain, Size: 2652 bytes --]
> In short, the literal maxint+1 is accepted because minint=-(maxint+1),
> and we don't have negative literals.
It looks strange that 4611686018427387904 is accepted (defect?), and OCaml
actually defines negative numeric literals according to
http://caml.inria.fr/pub/docs/manual-ocaml/lex.html
On the contrary, F# doesn't have negative numeric literals, but defines a
post-filtering of adjacent prefix tokens in 3.8.1. See
http://fsharp.org/specs/language-spec/3.0/FSharpSpec-3.0-final.pdf#page=28
Thanks
On Thu, Dec 3, 2015 at 12:49 AM, Gerd Stolpmann <info@gerd-stolpmann.de>
wrote:
> Thinking that this is a mostly aesthetic question, with one little
> exception:
>
> # max_int;;
> - : int = 4611686018427387903
> # -4611686018427387904;;
> - : int = -4611686018427387904
> # 4611686018427387904;;
> - : int = -4611686018427387904
> # 4611686018427387905;;
> Error: Integer literal exceeds the range of representable integers of
> type int
>
> In short, the literal maxint+1 is accepted because minint=-(maxint+1),
> and we don't have negative literals.
>
> However, the question is whether it is worth the trouble changing it. As
> you mention -safe-string, I just went through a large library and
> updated it, and it was far from trivial (needed GADTs) and a lot of work
> (something like 30 hours, really). I'm still skeptical whether changes
> of this kind get you a real benefit.
>
> Gerd
>
>
> Am Mittwoch, den 02.12.2015, 22:59 +0400 schrieb Stanislav Artemkin:
> > Hi all,
> >
> >
> > I've just stumbled upon yet another question about unary negation
> > parsing
> > (
> http://stackoverflow.com/questions/34044873/passing-negative-integer-to-a-function-in-ocaml
> ):
> >
> >
> > let f x = x + 1 in
> > f -1
> >
> >
> > is not valid in OCaml.
> >
> >
> > I'm just wondering why this issue is still not addressed in the
> > parser? For example, F# parses "f -1" as unary negation, but "f - 1"
> > and "f-1" as binary operator. It looks a bit tricky (as whitespace is
> > taken into account), but feels so natural when writing code.
> >
> >
> > Is there any reason we can't have the same in OCaml?
> >
> >
> > PS. I understand that it may break existing code, but it should be
> > solvable by a compiler option similar to -safe-string etc.
> >
> >
> > Thank you
> >
> >
>
> --
> ------------------------------------------------------------
> Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
> My OCaml site: http://www.camlcity.org
> Contact details: http://www.camlcity.org/contact.html
> Company homepage: http://www.gerd-stolpmann.de
> ------------------------------------------------------------
>
[-- Attachment #2: Type: text/html, Size: 4326 bytes --]
next prev parent reply other threads:[~2015-12-03 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 18:59 Stanislav Artemkin
2015-12-02 20:49 ` Gerd Stolpmann
2015-12-03 10:02 ` Stanislav Artemkin [this message]
2015-12-02 21:21 ` Mr. Herr
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='CAL4yAN=b_ihMvvErgFkSV3tMMhTSJfMibuDDJKZ-S4_iUMbFcg@mail.gmail.com' \
--to=artemkin@gmail.com \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
/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).