> The G.pm was made so that it's a NOOP (NO OPeration) under anything
> but windows. You may want to make sure it will not be even loaded by
>
> BEGIN {
> if ($^O eq 'MSWin32') {
> eval "use G;";
> }
> }
>
> If course it's up to you whether you have
> eval "use G;";
> or some glob() based code t
From: Bryan Harris <[EMAIL PROTECTED]>
> >> I'm sure this has been answered before, but I can't seem to find an
> >> answer.
> >>
> >> Windows doesn't seem to want to expand wildcards before passing
> >> arguments to my script. For example, typing:
> >>
> >> fixNCcode P*
> >>
> >> Passes 'P*'
>> I'm sure this has been answered before, but I can't seem to find an answer.
>>
>> Windows doesn't seem to want to expand wildcards before passing arguments to
>> my script. For example, typing:
>>
>> fixNCcode P*
>>
>> Passes 'P*' to my script instead of all files that start with "P".
>>
From: Bryan Harris <[EMAIL PROTECTED]>
> I'm sure this has been answered before, but I can't seem to find an
> answer.
>
> Windows doesn't seem to want to expand wildcards before passing
> arguments to my script. For example, typing:
>
> fixNCcode P*
>
> Passes 'P*' to my script instead of al
Bryan Harris wrote:
>
> I'm sure this has been answered before, but I can't seem to find an answer.
>
> Windows doesn't seem to want to expand wildcards before passing arguments to
> my script. For example, typing:
>
> fixNCcode P*
>
> Passes 'P*' to my script instead of all files that start
I'm sure this has been answered before, but I can't seem to find an answer.
Windows doesn't seem to want to expand wildcards before passing arguments to
my script. For example, typing:
fixNCcode P*
Passes 'P*' to my script instead of all files that start with "P".
Is there a workaround? H
