Chris Devers <[EMAIL PROTECTED]> wrote on 1/10/02 at 10:03a: > Still though, I'm really confused by the line endings issue on OSX. It > seems like a lot of programs -- low level BSD stuff and high level Mac > stuff alike -- have to either become consistent or agnostic in the way > they handle line endings, and I'm not at all sure what the best way to > resolve this is on a general level. Inheriting two more or less opposite > conventions has been making things way too messy...
BBEdit makes this a lot easier. If you run Perl scripts (or any other Unix scripts, for that matter) from within BBEdit, it does the right thing behind the scenes to make sure the file sent to the Perl interpretter has "native" line endings. If you're on Mac OS X, and your script already has Unix line endings, BBEdit just passes the file off to perl. If the script has Mac or DOS line endings, BBEdit writes out a temp file with Unix endings and sends that to perl. (BBEdit is about as agnostic about line endings as an editor can get.) Vice versa on Mac OS 9; BBEdit will convert a script with Unix or DOS line endings to Mac endings before being passed off to MacPerl for execution. I don't think the Darwin toolset is ever going to change (nor should it); Unix tools expect Unix line endings. And the high level stuff needs to remain compatible with Mac OS 9, at least for next few years, and that means Mac line breaks. -- John Gruber [EMAIL PROTECTED]
