> I've actually patched the docs to say that it will look at $ENV{PATH}
> or the local equivalent. I think this is best, because the
> caller code shouldn't have to figure out what string to pass it.
This isnt the point. Its not an uncommon situation to need to split a path like variable in a platform intelligent way.
Consider that perl itself has several such variables. PERLLIB and PERL5LIB.
If you dont provide a way for a user to pass in variables to split then the routine is not generally useful and people will be reinventing this particular wheel (and probably badly) every time they have a path like variable in their config file or whatever.
I suppose one could always say
my @parts=do {
local $ENV{PATH}=$the_path_i_need_split;
File::Spec->path()
};
but personally I think thats ridiculous.
> It already looks at $ENV{PATH}, $ENV{Path}, and $ENV{path} for Win32,
> since before I started maintaining the module.
As regarding looking at $ENV{PATH} and $ENV{Path} and $ENV{path} I dont understand this. All three return the same thing. ENV settings on Win32 arent case sensitive.
Cheers,
Yves
