New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"\" does not escape meta chars if also delim #12144
Comments
From @ikegamiCreated by @ikegamiAbout "\", perlre says: "Quote the next metacharacter." "So anything that looks like \\, \(, \), \<, \>, \{, or \} is always "Any single character matches itself, unless it is a metacharacter with a Yet when "\" is used to escape a char that's both delimiter and meta, the
- Eric Perl Info
|
From @demerphqOn 29 May 2012 08:39, Eric Brine <perlbug-followup@perl.org> wrote:
I dont think this is a bug, but I do plan to work on changing it to DWIM. Yves -- |
The RT System itself - Status changed from 'new' to 'open' |
From vadim.konovalov@alcatel-lucent.com
what is DWIM here? IMO - if anything - an explanation that Eric refers should be expanded |
From @demerphqOn 29 May 2012 09:56, Konovalov, Vadim (Vadim)** CTR **
DWIM is that an escaped metacharacter that happens to match a Yves -- |
From @ikegamiOn Tue, May 29, 2012 at 3:48 AM, demerphq <demerphq@gmail.com> wrote:
You pointed out elsewhere that perlop documents the actual behaviour. When the docs don't agree with what actually happens, it's a bug. When the docs don't agree with each other, it's a bug. The bug could be as simple as: perlre talks about literals/operators when On Tue, May 29, 2012 at 3:56 AM, Konovalov, Vadim (Vadim)** CTR ** <
This can be addressed by simply removing from perlre, although that would - Eric |
From @demerphqOn 29 May 2012 10:49, Eric Brine <ikegami@adaelis.com> wrote:
The docs seem to agree with what actually happens.
I haven't so far been convinced that the docs disagree with each I mean, we are kinda quibbling here as we both agree the behavior
Interesting angle. Yves -- |
From @cpansproutOn Tue May 29 00:49:24 2012, demerphq wrote:
I think that will break a lot of code. -- Father Chrysostomos |
From @dmcbrideOn Tuesday May 29 2012 9:18:06 AM Father Chrysostomos via RT wrote:
Honestly, I would have expected the need to extra-escape in the second m.\\\.. However, as has been pointed out already, this doesn't (currently) work, I'm not sure fixing that would break much/any code in practice. And I'm not $dot = qr/\./; or m.[\.]. |
From @demerphqOn 29 May 2012 18:18, Father Chrysostomos via RT
Hrm, I hope not. At least no less than say, retiring the empty pattern. OTOH, that comment might make it just a bit easier to say "it's too cheers -- |
From @cpansproutOn Tue May 29 13:15:11 2012, demerphq wrote:
I’ve known about that aspect of parsing for about eight years. I learnt Since then, I’ve written regular expressions with that in mind, thinking I tend to pick my delimiters more or less at random, so I won’t be This is the sort of change that worries me.
:-) -- Father Chrysostomos |
From 2bfjdsla52kztwejndzdstsxl9athp@gmail.comQuoth Darin McBride:
or even m.\Q\.\E. /Bo Lindbergh |
Migrated from rt.perl.org#113420 (status was 'open')
Searchable as RT113420$
The text was updated successfully, but these errors were encountered: