good chemistry is complicated, and a little bit messy -LW |
|
PerlMonks |
Re: (tye)Re: line endings in remote documentsby Juerd (Abbot) |
on Dec 20, 2001 at 23:45 UTC ( [id://133581]=note: print w/replies, xml ) | Need Help?? |
Yes, the default for $/ is \n on all platforms. The wicked thing is that \n isn't the same for all platforms. If you need to be sure about what character you'll get, use chr(), \xhex, \oct or \cchar. If you don't know if your data came from the same platform as your script, you can only try using a regex like \r\n?|\n to match every known newline. I quote from perlop: All systems use the virtual "\n" to represent a line terminator, called a "newline". There is no such thing as an unvarying, physical newline character. It is only an illusion that the operating system, device drivers, C libraries, and Perl all conspire to preserve. Not all systems read "\r" as ASCII CR and "\n" as ASCII LF. For example, on a Mac, these are reversed, and on systems without line terminator, printing "\n" may emit no actual data. In general, use "\n" when you mean a "newline" for your system, but use the literal ASCII when you need an exact character. For example, most networking protocols expect and prefer a CR+LF ("\015\012" or "\cM\cJ") for line terminators, and although they often accept just "\012", they seldom tolerate just "\015". If you get in the habit of using "\n" for networking, you may be burned some day.
In Section
Seekers of Perl Wisdom
|
|