[Boston.pm] '/' =~ m\/\b; (bug?)

2006-11-15 Thread Carl Eklof
Hi Guys n Gals, I have found some seemingly strange behavior that may be of interest to this list. My assumption was that the \b pattern in a regex would always match the beginning and end of a string (as documented in the perlre page). However on my build of 5.8.7 this is not the case if the

Re: [Boston.pm] '/' =~ m\/\b; (bug?)

2006-11-15 Thread Ronald J Kimball
On Wed, Nov 15, 2006 at 02:05:47PM -0800, Carl Eklof wrote: Hi Guys n Gals, I have found some seemingly strange behavior that may be of interest to this list. My assumption was that the \b pattern in a regex would always match the beginning and end of a string (as documented in the

Re: [Boston.pm] '/' =~ m\/\b; (bug?)

2006-11-15 Thread Ben Tilly
On 11/15/06, Carl Eklof [EMAIL PROTECTED] wrote: Hi Guys n Gals, I have found some seemingly strange behavior that may be of interest to this list. My assumption was that the \b pattern in a regex would always match the beginning and end of a string (as documented in the perlre page).

Re: [Boston.pm] '/' =~ m\/\b; (bug?)

2006-11-15 Thread Carl Eklof
Thanks to both Ben, and Ronald for correcting me. I had misunderstood the documentation. I do expect that others may also think that using $string =~ /\b$sub_str\b/ is a reasonable way to match a substring on word-boundaries, or beginning/end of the string, but hopefully they will realize the

Re: [Boston.pm] '/' =~ m\/\b; (bug?)

2006-11-15 Thread Uri Guttman
CE == Carl Eklof [EMAIL PROTECTED] writes: CE My assumption was that the \b pattern in a regex would CE always match the beginning and end of a string (as CE documented in the perlre page). However on my build of CE 5.8.7 this is not the case if the character being CE matched at the