Re: [MacPerl] Using UNIX style filenames with MacPerl

[Greg Aiken <grega9@idt.net>]

Thats great if you only need to work with certain files and don't need to do
much with directories.  You've obviously not needed to do alot of moving around
within directories in any of your applications.  Creating new directories (as
well as testing to see if these exist before you attempt to make them) and
moving about within directory structures most certainly could be done by
breaking each directory traversal into a series of single 'cd ..' and 'cd
new_sub' commands, but even you must agree that this is clunky.

My angle on this is that MacPerl strayed from the concrete reference core Perl
design.  Why change the directory delimiter from '/' to ':' anyway?  None of
this would have been an issue if this hadn't happened.  Although its hard to
gripe at the author of this fine contribution to the Mac platform - beggars
can't be choosers.


Douglas P. McNutt wrote:

> To: mac-perl@iis.ee.ethz.ch
>
> Dogcow it. This whole problem comes about because of sloppy coding both by
> UNIX and Mac perl scripters. I just went back through ALL of the perl
> scripts I have ever written. There isn't a single case of a hard-coded file
> name in them. I pass the file names as arguments or look them up as
> environment variables. They thus take the required form regardless of the
> underlying system.
>
> Fixed file names are almost the equivalent of assuming a date is 19xx.
>
> Perhaps the most important thing is to get a GOOD way of passing system
> specific filenames to the application version of MacPerl. That way a
> well-written UNIX script won't have to worry about filenames.
>
> -> From the USA. The only socialist country that refuses to admit it. <-
>
> ***** Want to unsubscribe from this list?
> ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch




***** Want to unsubscribe from this list?
***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch