Re: [MacPerl-Porters] [PATCH cfgperl 6212] MacOS regression suite mods

[Matthias Neeracher <neeri@iis.ee.ethz.ch>]

In article <p0432040ab56970c5605d@[192.168.0.77]>, Chris Nandor <pudge@pobox.com> writes:
> At 12.47 -0700 2000.06.09, Peter Prymmer wrote:
> As to doing some filespec conversion
> natively, heck, we already have some translation of / in paths (%INC and
> requires):

>    require "Foo/Foo.pm";  # works in MacPerl now

> I am personally not much in favor of this, though.  For years I had a main
> directory with "/" in the name.  You can change it to "%2F", but now what
> about all those routines that recognize each part of a filename as being
> only 31 characters long?  What about File::Spec and File::Basename parsing
> of these?  It seems like more confusion in some respects in exchange for
> less in others.

> So anyway, I would like to know what would happen if I wrote this:

>   use lib "Bourque:WP/DTP:lib:";

> I've since changed the directory name to avoid such conflicts, but for many
> years, that's what it was, and I wouldn't be at all surprised if people had
> "HD:Programming/Coding:MacPerl:" directories.

What I've implemented now is:

 - Any calls which potentially could create a file/directory never do
   translation (that means that I won't do open, just require and @INC).
   I'm not entirely sure about the -x operators, but currently, I don't
   translate for them.
 - The native MacOS interpretation has predecence.
 - The translation is only tried if the native interpretation fails.

With these restrictions, I think it's safe to translate in the cases where I do
it.

Matthias

-- 
Matthias Neeracher   <neeri@iis.ee.ethz.ch>   http://www.iis.ee.ethz.ch/~neeri
  "And that's why I am going to turn this world upside down, and make
   of it a fire so *bright* that someone real will notice"
                                -- Vernor Vinge, _Tatja Grimm's World_

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