Interestingly enough, if you use a named parameter class instead of a the \s assertion, it finds it correctly in both strings.

$ascii = "\xa0\x{a0}";
$unicode = "\x{100}\xa0\x{a0}";

print "Latin-1 \\s : ",  $ascii =~  /\s/ ? "yes":"no","\n";
print "Latin-1 \\p{Space}: ",  $ascii =~  /\p{Space}/ ? "yes":"no","\n
+\n";


print "Unicode \\s: ",$unicode =~ /\s/ ? "yes":"no","\n";
print "Unicode \\p{Space}: ",$unicode =~ /\s/ ? "yes":"no","\n";

[download]

I certainly wouldn't expect non-breaking space to be recognized or not as a space depending on what else was in the string.

(I even experimented with whether the enclosing brackets were significant... apparantly not.)

In reply to Re: inconsistency in whitespace handling by thundergnat
in thread inconsistency in whitespace handling by Skeeve

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.