From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: William Smith <bills@emu-bark.com>, Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] modified error messages for ocamlc
Date: Sun, 14 Apr 2013 19:06:35 +0200 [thread overview]
Message-ID: <CAPFanBEe7vT8z3b-hPJWhq1JCbFqAcftV2Q+PS9T_-_q537Tdw@mail.gmail.com> (raw)
In-Reply-To: <A1F099272F714E17B019C4C065ADF12E@erratique.ch>
>> Would there be any interest in me making the change everywhere and submitting it as a patch?
>
> Not at all...
I'm not sure if this is a language barrier thing, or sarcasm/irony
that got lost on the wire, but my personal reaction would rather be
that there indeed is some interest, especially if you follow Daniel's
excellent suggestion to respect the standard GNU format for that.
On a related note, I have put in
http://caml.inria.fr/mantis/view.php?id=5044 some hooks for Emacs
compile-mode to parse additional error messages that are not supported
by default, namely the backtrace format and the location printed in
the 'assert false' error message. This is so convenient that I often
feed "ocamlbuild test.byte && ./test.byte" as my compilation command
in my edit-compile-test cycles.
On Sun, Apr 14, 2013 at 6:25 PM, Daniel Bünzli
<daniel.buenzli@erratique.ch> wrote:
> Le dimanche, 14 avril 2013 à 16:20, William Smith a écrit :
>> Would there be any interest in me making the change everywhere and submitting it as a patch?
>
> Not at all...
>
>> One concern I have is that it might break automated test scripts.
>
> That may be the case but more importantly your fancy way of reporting error messages is not recognized by emacs' compilation-mode. ocaml's current way of reporting allows compilation-mode to perfectly hilight the span of the error in your source *without* having to tweak the `compilation-error-regexp-alist` variable. That's not the case of your format.
>
> If something has to be changed I'd rather have the gnu standard way of reporting errors for ranges [1] which is both more compact and recognized by emacs' compilation-mode.
>
> Best,
>
> Daniel
>
> [1] http://www.gnu.org/prep/standards/standards.html#Errors
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2013-04-14 17:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 15:20 William Smith
2013-04-14 16:25 ` Daniel Bünzli
2013-04-14 17:06 ` Gabriel Scherer [this message]
2013-04-14 17:57 ` Daniel Bünzli
2013-04-14 18:19 ` Jonathan Protzenko
2013-04-14 19:18 ` Daniel Bünzli
2013-04-14 20:01 ` [Caml-list] " Christopher Zimmermann
2013-04-15 15:37 ` [Caml-list] " Jacques Le Normand
2013-04-15 6:26 ` Raphaël Proust
2013-04-16 0:32 ` [Caml-list] " Stefan Monnier
2013-04-18 16:40 [Caml-list] " William Smith
2013-04-21 7:37 ` Gabriel Scherer
2013-04-21 10:53 ` Daniel Bünzli
2013-04-21 11:28 ` Gabriel Scherer
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=CAPFanBEe7vT8z3b-hPJWhq1JCbFqAcftV2Q+PS9T_-_q537Tdw@mail.gmail.com \
--to=gabriel.scherer@gmail.com \
--cc=bills@emu-bark.com \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
/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