in reply to Re^2: Pattern Matching in Cygwin Perl vs. Win32 Perl
in thread Pattern Matching in Cygwin Perl vs. Win32 Perl
Isn't it better to know?
Furthermore, perlport saysC:\>perl -le"print $/" | od -tacx1 0000000 cr nl cr nl \r \n \r \n 0d 0a 0d 0a 0000004 C:\>perl -le"print unpack q,H*,,$/" | od -tacx1 0000000 0 a cr nl 0 a \r \n 30 61 0d 0a 0000004 C:\>
In most operating systems, lines in files are terminated by newlines. +Just what is used as a newline may vary from OS to OS. Unix tradition +ally uses \012, one type of DOSish I/O uses \015\012, and Mac OS uses + \015. Perl uses \n to represent the "logical" newline, where what is logical + may depend on the platform in use. In MacPerl, \n always means \015. + In DOSish perls, \n usually means \012, but when accessing a file in + "text" mode, STDIO translates it to (or from) \015\012, depending on + whether you're reading or writing. Unix does the same thing on ttys +in canonical mode. \015\012 is commonly referred to as CRLF.
|
|---|