From: "Mattias Engdegård" <mattiase@acm.org>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 18109@debbugs.gnu.org
Subject: bug#18109: 24.4.50; `compilation-error-regexp-alist-alist': wrong regexp for Maven
Date: Mon, 7 Dec 2020 14:49:40 +0100 [thread overview]
Message-ID: <133EE4BE-AD7E-4197-9888-1E4CCC47BB90@acm.org> (raw)
In-Reply-To: <m25z5dj3ui.fsf@fastmail.fm>
7 dec. 2020 kl. 11.41 skrev Filipp Gunbin <fgunbin@fastmail.fm>:
> It was me who put there those quantifiers, and I don't object to making
> the regexps stricter.
It would be unfair to blame you for that! After all, that's how most of the other patterns were written, and for logical reasons: it seems intuitive and sensible to make the rules as loose as possible in case the format changes or there is otherwise a variation in the output. If the observed messages contain a single space in one place then standard practice has been to tolerate any number of spaces there, maybe even zero.
However, experience tells us that this intuition is wrong. Output formats do in fact tend to remain unchanged: Emacs and other editors, IDEs and other code are parsing them, and they are not all equally tolerant or in the same way. There is thus a self-reinforcing effect: the tool keeps output stable because we expect it to. (When output formats do change, it tends to be for good reasons and regexp tolerance is then rarely useful.)
> But, we just need to be aware that Java tools usually don't expect the
> output to be parsed.
Yes they do! The very composition of something like the gradle-kotlin output
e: FILENAME: (LINE, COL): MESSAGE
is so strict and formalised that it was definitely made with machine-readability in mind.
> That is why I'm more inclined to
> making regexps more _lax_, not the other way around (and fix the
> problems with them once they appear).
As we have found out the hard way, the cost of lax patterns is insidious and diffuse until the mess really has to be sorted out -- and by then it's hard to get hold of the various people involved who have since long disappeared or forgot all about what they wrote years ago. Patterns are added independently of one another but interact in unexpected ways.
Thus, better to keep patterns strict, and only alter them when and if tool output changes; it is then clear exactly what needs to be done and why. For most rules this never becomes necessary.
next prev parent reply other threads:[~2020-12-07 13:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 17:33 bug#18109: 24.4.50; `compilation-error-regexp-alist-alist': wrong regexp for Maven Filipp Gunbin
2014-07-26 7:22 ` Glenn Morris
2014-07-28 12:30 ` Filipp Gunbin
2014-08-03 15:12 ` Daniel Colascione
2020-09-09 11:16 ` Lars Ingebrigtsen
2020-12-03 14:59 ` Lars Ingebrigtsen
2020-12-04 18:11 ` Filipp Gunbin
2020-12-04 19:22 ` Mattias Engdegård
2020-12-05 22:21 ` Filipp Gunbin
2020-12-06 9:32 ` Mattias Engdegård
2020-12-06 14:22 ` Filipp Gunbin
2020-12-06 15:05 ` Mattias Engdegård
2020-12-06 15:25 ` Mattias Engdegård
2020-12-07 10:41 ` Filipp Gunbin
2020-12-07 13:49 ` Mattias Engdegård [this message]
2020-12-07 20:07 ` Filipp Gunbin
2020-12-09 18:41 ` Mattias Engdegård
2020-12-10 13:12 ` Filipp Gunbin
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=133EE4BE-AD7E-4197-9888-1E4CCC47BB90@acm.org \
--to=mattiase@acm.org \
--cc=18109@debbugs.gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=larsi@gnus.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.