From: Joshua Branson <jbranso@dismail.de>
To: 34085@debbugs.gnu.org
Subject: bug#34085: autoscan reports a warning
Date: Thu, 17 Jan 2019 10:04:38 -0500 [thread overview]
Message-ID: <87imynnx4p.fsf@dismail.de> (raw)
In-Reply-To: <20190116172916.20b20636@scratchpost.org> (Danny Milosavljevic's message of "Wed, 16 Jan 2019 17:29:16 +0100")
Danny Milosavljevic <dannym@scratchpost.org> writes:
> Hi,
>
> On Tue, 15 Jan 2019 10:43:49 -0500
> Joshua Branson <jbranso@dismail.de> wrote:
>
>> I'm not certain if this is the right list to report this to, but I just
>> installed autoscan version 2.21, and it gave me this warning:
>>
>> #BEGIN_SRC sh
>> autoscan
>> #END_SRC
>>
>> Unescaped left brace in regex is deprecated here (and will be fatal
>> in Perl 5.30), passed through in regex; marked by <-- HERE in m/\${
>> <-- HERE [^\}]*}/ at /home/joshua/.guix-profile/bin/autoscan line
>> 361.
>>
>>
>> Should I report this upstream instead?
>
> I think so, yes.
>
> autoscan is part of autoconf 2.21, so the bug report should go to the autoconf package.
>
> The regexp in question is
>
> s/\${[^\}]*}//g;
>
> Perl is complaining because perl regexp use curly braces to specify a range of valid repeats.
> Maybe the easiest way to understand it is that the following equivalences hold in regexps:
>
> ? is equivalent to {0,1}
> + is equivalent to {1,}
> * is equivalent to {0,}
>
> The above (at the end of the regexp "\${[^\}]*}") probably means a literal curly
> brace--but they don't escape it - hence the warning.
>
> It's only a warning because no valid repeat range can start with a closing curly
> brace.
> So perl can still figure out what you meant.
>
> But it's obviously not recommended to use unescaped closing curly braces to
> match a literal closing curly brace regardless.
>
Ok, I'll report this upstream. Thanks for flushing out the main issue!
--
Joshua Branson
Sent from Emacs and Gnus
prev parent reply other threads:[~2019-01-17 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 15:43 bug#34085: autoscan reports a warning Joshua Branson
2019-01-16 10:55 ` Ludovic Courtès
2019-01-16 16:29 ` Danny Milosavljevic
2019-01-17 15:04 ` Joshua Branson [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imynnx4p.fsf@dismail.de \
--to=jbranso@dismail.de \
--cc=34085@debbugs.gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).