And, as a further guess, the way $self->{ABSTRACT} is assigned its value, has something to do with it.

It's all very strange.
I, in fact, did get to wonder whether the change was in the assignment of $self->{ABSTRACT}, and *not* in the behaviour of $self->{ABSTRACT} =~ m![[:cntrl:]]+!
However, I didn't really look at how the former was being assigned.

If I could reproduce the issue I reckon I'd be wanting to understand it.
But I can't reproduce it ... so it's really not all that important to me. (I guess I just find it "intriguing" rather than "important".)

To satisfy my own curiosity, I fiddled about with the following script, on both Linux and Windows:

use strict;
use warnings;

my $count = 0;

for my $s(chr(13) . chr(10),
          chr(10) . chr(13),
          chr(10)          ,
          chr(13)          ,
          '0' . chr(13) . chr(10),
          '0' . chr(10) . chr(13),
          '0' . chr(10)          ,
          '0' . chr(13)          , ) {

    $count++;  
    print "$count match\n" if ($s && $s =~ m![[:cntrl:]]+!);
}
[download]

But it just outputs:

1 match
2 match
3 match
4 match
5 match
6 match
7 match
8 match
[download]

on every perl I run it on.
So I don't understand how a lone \r is being treated differently to a lone \n or \r\n in some cases for you.

Cheers,
Rob

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.