From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: William Smith <bills@emu-bark.com>
Cc: Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] modified error messages for ocamlc
Date: Sun, 14 Apr 2013 17:25:43 +0100 [thread overview]
Message-ID: <A1F099272F714E17B019C4C065ADF12E@erratique.ch> (raw)
In-Reply-To: <516AC928.9030400@emu-bark.com>
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
next prev parent reply other threads:[~2013-04-14 16:25 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 [this message]
2013-04-14 17:06 ` Gabriel Scherer
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=A1F099272F714E17B019C4C065ADF12E@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=bills@emu-bark.com \
--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).