Re^4: bracket processing

... for regexes in general, that's fine ... bracketed classes are different. ... Most characters that are meta characters in regular expressions ... lose their special meaning ... none of the characters in $delim required escaping.

In a character class, no one can hear your metacharacters scream. For the most part. The consequences of the occasional exception are what I seek to avoid with defensive measures like this. The effects of a change from
my $delim = '([{<';
to
my $delim = '(-[{<';
may not be readily apparent, yet still be very significant. One would hope that thorough testing would reveal a problem like this, but better IMHO to obviate the problem to begin with.

Give a man a fish: <%-{-{-{-<

Comment on Re^4: bracket processing Select or Download Code

Replies are listed 'Best First'.
Re^5: bracket processing by kcott (Archbishop) on Apr 02, 2020 at 01:44 UTC
"... a change from `my $delim = '([{<';` to `my $delim = '(-[{<';` may not be readily apparent ..." I find it hard to believe that you think that range of 52 characters "may not be readily apparent". `$ perl -E 'say "@{[map chr, ord q{(} .. ord q{[}]}"' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J +K L M N O P Q R S T U V W X Y Z [` [download] The OP hadn't asked for a hyphen to take on a parenthetical function; however, if that was wanted, the correct way to write it would be: `my $delim = '([{<-';` [download] And still nothing needs to be escaped. What you've contrived as an example is a novice mistake. It's a good mistake to learn from. I'm sure I made that mistake a quarter of a century ago; found out what I did wrong; and, didn't do it again. Defensive programming is all well and good when dealing with data from an unknown or untrusted source. When the data is just four characters you've written yourself; defensive programming is overkill. — Ken	[reply] [d/l] [select]
Re^6: bracket processing by AnomalousMonk (Archbishop) on Apr 02, 2020 at 03:16 UTC
You have the wisdom and discipline (and steel-trap memory, apparently :) to make a mistake once and never make it again. I saw long ago that I had not. One of the lessons I drew from that observation was to program defensively. Even when I have absolute control of both code and data, however simple, I find the effort of defensive programming is usually, in the end, repaid. Defensive programming is all well and good when dealing with data from an unknown or untrusted source. When the data is just four characters you've written yourself; defensive programming is overkill. It's been observed time and again that one is oneself the person best equipped to lead one down the garden path. What you've contrived as an example is a novice mistake. It's a good mistake to learn from. I should have made it clear in my initial comment that it was not intended for you; I think you are well aware of the issues involved. It's hard to contrive an example of a novice mistake that's not... well, contrived, but please be assured that the example in question was directed not to you but to novices. Give a man a fish: `<%-{-{-{-<`	[reply] [d/l]