> so I guess the question is - presume that it is either or > and rip them all out before proceding anyway????
IMHO I think one should presume that it is that way...Thats why we go to the trouble to have standards isnt it? so that everyone doesnt have to go around doing custom work for every different OS and application? If programmers go out of their way to pick up after slackers who dont conform to the w3, doesnt that defeat the purpose of the w3? take a stand, a small stand albeit, but a stand nevertheless :) btw...does anyone know of a browser that DOESNT conform to the cr/lf for newlines? Is anyone bored enough to go look? > > what I am not getting in these debates is why one should do > > my $cr = chr(13); > my $lf = chr(10); > my $eol = "$cr|$lf"; > > as opposed to leaving it to perl as > > my $eol = '\r|\n'; > > for tricks like: > > my $pat= qr/[$eol]+/o; > If the latter method works, that's cool, i havent tested it. I will admit that as I learn this stuff, I tend to do everything the hard way first, then trim it down. Cheers J- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
