From: Daniel Colascione <daniel@censorshipresearch.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Emacs-devel@gnu.org
Subject: Re: [PATCH] eliminate false positive in compile.el
Date: Thu, 25 Mar 2010 15:49:19 -0400 [thread overview]
Message-ID: <4BABBE3F.6050402@censorshipresearch.org> (raw)
In-Reply-To: <jwvpr2sb8i3.fsf-monnier+emacs@gnu.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 3/25/10 3:24 PM, Stefan Monnier wrote:
>> -\[0-9]?\\(?:[^0-9\n]\\|$\\)\\|[0-9][0-9][0-9]\\)"
>> +\[0-9]?\\(?:[^0-9\n]\\)\\|[0-9][0-9][0-9]\\)"
>
> which simplifies to
>
> \[0-9]?[^0-9\n]\\|[0-9][0-9][0-9]\\)"
Right; I just figured I'd make the change minimal.
>
> Could you give some rationale for this change other than just "eliminate
> false positive"? I mean, someone went to the trouble to add the
> \\(?:...\\|$\\), so there should be a good reason to remove it,
Well, I prefer to not match "included from" lines from gcc, but with the
current gnu compile matcher, it's impossible not to do that. What these
lines all have in common is that they end with ":" or ":,". gnu doesn't
match the latter, but it does match the former, which is always the last
line before the real error message.
By removing |$, we prevent the gnu matcher from matching compile error
lines that appear to have an empty message, which fixes the above issue.
The gcc-include matcher does catch the "included from" lines if people
want to use it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
iEYEARECAAYFAkurvj8ACgkQ17c2LVA10VtzqwCdH70b7c4C8PI16DNNBCh1fIm/
j9UAn365appc78wzgCaPB324IltUUk57
=U7eK
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-03-25 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 4:07 [PATCH] eliminate false positive in compile.el Daniel Colascione
2010-03-25 19:24 ` Stefan Monnier
2010-03-25 19:49 ` Daniel Colascione [this message]
[not found] ` <201003252103.o2PL3PuE006566@godzilla.ics.uci.edu>
2010-03-25 21:05 ` Daniel Colascione
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BABBE3F.6050402@censorshipresearch.org \
--to=daniel@censorshipresearch.org \
--cc=Emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).