So it ought to remove both CR and LF on Windows, I think.
Isn't it better to know?
C:\>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:\>
Furthermore, perlport says
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.
-
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.
|