[Date Prev][Date Next][Thread Prev][Thread Next] [Search] [Date Index] [Thread Index]

Re: [MacPerl] MacPerl bugs?



At 5:14 AM -0400 6/24/99, Joshua Juran wrote:

} At 7:16 PM -0400 1999-06-07, Chris Nandor wrote:
} >At 19.03 -0400 1999.06.07, Joshua Juran wrote:
} >
} >$^O, not $^0.  And the answer is undefined.  When someone does it, they
} >would probably go onto the perl porters mailing list and it would be
} >discussed.  I frankly think it would be a bad idea, but to each his own.  I
} >do have a question for you, though: what could possibly be changed about
} >MacPerl's stat output?  The only nonstandard thing about it is atime and
} >mtime are the same, because there is no atime data stored on Mac OS.  Do
} >you want to rewrite the filesystem?
}
} You're right, the perl porters list is the place to discuss it.  But since
} you asked, perl's stat return's mtime as seconds since 1970, versus
} MacPerl's 1904.  And yes, I intend to rewrite the filesystem.  One of my
} projects is to write a command shell for Mac OS, as well as a development
} environment that is as POSIX-like as can be arranged.  The point?  To allow
} deployment of unix-based software with minimal or no revision.  Since many
} programs assume a unix filing system, that project calls for implementing
} one.

You mean like MachTen?  I'm curious.  I can't imagine anyone writing such a
thing at this point of time, because there are so many ways of getting
Unix-like on Mac hardware or even under MacOS these days, and by the end of
the year, you'll be able to purchase Macs with BSD installed on them.
What's the point of doing it again?

}
} It was relatively simple to handle DOS text files by stripping leading
} linefeeds.  But how would I handle unix text files without knowing in
} advance that's what they are?  I guess I can check for a linefeed at the
} end (or anywhere, just in case) in the first line.  (DOS files don't have
} linefeeds before the first CR.)  If so, reset the file and set LF as the
} newline char.  Sounds like a pain, though, and slurps in the whole file at
} first.  Any better ideas?

Read a small fixed block (I usually do 2048), count \015 and \012, set $/
appropriately.  It's straightforward to implement.

}
} Josh
}
} --
} Joshua Juran                          Metamage Software Creations
} =)                                         Tools for Wizards
} wanderer@metamage.com
} <http://www.metamage.com/>   * Creation at the highest state of the art *
}
}

-----
Paul J. Schinder
schinder@pobox.com

===== Want to unsubscribe from this list?
===== Send mail with body "unsubscribe" to macperl-request@macperl.org