Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Gary R Van Sickle" To: "Cygwin Mailing List \(E-mail\)" Subject: Re: perl & \n (was: perl-5.8.0 breaks code "working" on 5.6.1 over "\n" Date: Mon, 22 Jul 2002 13:12:18 -0500 Message-ID: <000a01c231ab$51753680$2101a8c0@BRAEMARINC.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Gerrit P. Haase wrote: > notepad is the only application on earth that cannot handle \n as a > linefeed as every other editor does. Which other applications did I > missed to hate? Unfortunately that's only the tip of the proverbial iceberg. How many Unixoid apps choke on \r\n's? Or (heaven forbid we forget those still in MacLand) just \r's? Until Cygwin came along, I'd guess probably all of them. fseek()ing all over hell, cat'ing binaries, lordy. It's almost beyond belief that here it is, the fricken' 21st century, and we even have to care what the stupid line endings in our *text* files are. Do I worry about what the moral equivalent of "line endings" are in a JPEG? Nope. An MP3? Never even crossed my mind. But older-than-dirt ASCII text files? Holy Christ, get out the slide rules and keep the coffee comin', it's gonna be an all-nighter! Ok, rant off. I guess the only solution here is for me to get off my kiester and finish my Grand Unified Text File Library. I just hope I get the source code's line endings right. ;-) -- Gary R. Van Sickle Braemar Inc. 11481 Rupp Dr. Burnsville, MN 55337 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/