Re: Replacing new line characters from HTML TEXTAREA submissions

Sometimes I'll use the regular expression:

 $info=~s/[\n\r]{1,2}/<p>/gms;
or
 $info=~s/[\n\r]+/<p>/gms;
[download]

Maybe it is a bit too greedy for some people but for me, ack, one more newline and/or carriage returns is enough for a P tag.

I just noticed that your regular expression was just /g, keep in minde it WILL stop matching on the first line. You gotta let 'er match the entire string.

Comment on Re: Replacing new line characters from HTML TEXTAREA submissions Download Code

Replies are listed 'Best First'.

Useless use of /s and /m in a harmless context
by dvergin (Monsignor) on Mar 15, 2001 at 01:39 UTC

...it WILL stop matching on the first line.
You gotta let 'er match the entire string.

Nope. (Did you test your assertion before posting?)

Viz:

     my $s = "line1\r\nline2\r\nline3\r\n";
     print $s;
     $s =~ s/[\n\r]//g;
     print $s;
[download]

     line1
     line2
     line3
     line1line2line3
[download]

Here's what both perlman:perlre and/or a quick test script will show you:

   /s simply allows . to match end-of-line chars 
       anywhere in the string (if needed)
   /m simply allows ^ and $ to match begin/end
       of lines in mid-string instead of only
       the begin/end of the entire string.
   /g is happy to repeat searching over several lines
  m// (simple search) will find something that
       occurs on a line after the first one
   \n
   \r will both be found (if present) without
       resorting to /s or /m
[download]

[reply]
[d/l]
[select]


go ahead... be a heretic
	PerlMonks