Re: You don't always have to use regexes

A proper translation of if ( $value =~ /^true$/i ) would be:

if ( lc $value eq "true" || lc $value eq "true\n" )
[download]

(except that the former potentially sets $&, $`, and $' and the last-successful-regex).

Comment on Re: You don't always have to use regexes Select or Download Code

Replies are listed 'Best First'.
Re^2: You don't always have to use regexes by petdance (Parson) on Feb 25, 2005 at 03:02 UTC
Yes, but that check for "\n" is really irrelevant. It's required to be functionally identically, but not semantically. Semantics are the real issue here. The regex is saying "Do you have a string that matches the beginning of the string, then t, r, u, e and then the end of the string", and the compare is saying "Is the string the word 'true'?" "Is this the word I want" is the real intent. xoxo, Andy	[reply]
Re^3: You don't always have to use regexes by ysth (Canon) on Feb 25, 2005 at 04:01 UTC
My point was that that is not what the regex is saying. Just my own personal bonnet-bee, but people misinterpret $ way too often, and I feel it deserves publicity whenever it comes up.	[reply]