le way to do this. But several
days of experimenting have been unsuccessful.
Advice appreciated!
Rick Triplett
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
Many thanks to Scott, Shawn, Paul, Jenda, and Uri. I've learned
something from each of you, and appreciate your taking the time to help!
Rick
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
d help. Or maybe I need a whole new
approach? I can try this out, but it will take weeks to get enough
results to see if it works. Any suggestions would be greatly
appreciated.
Rick Triplett
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTE
fied the
line endings as \r.
My perplexities are these: Why did TextWrangler show \r for the line
endings after I had save them for Unix (\n)? And, why did Perl have
difficulty with the line endings in the first place? Perl is supposed
to be sensitive to the operating system it is running on and "do the
right thing."
Rick Triplett
I shared this thread with the support people at Bare Bones Software.
This was their reply:
Hi Rick,
TextWrangler always uses \r (ASCII 13, the canonical carriage return)
internally, but you can tell it to use any desired representation on
disk for the line endings: Mac (CR), Unix (LF), or
