On Tue, Oct 25, 2005 at 03:59:44PM -0400, Will Coleda wrote:
> I think that module is small enough and useful enough for the build
> process to include in parrot if we need to (and copying it in is
> better than rewriting it from scratch), but...
>
> I think this would be a good time (esp. af
On 10/25/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> File::Which is a rather small amount of code in a single file so I'd be
> inclined to include it in the Parrot tree rather then reinventing the
> wheel. I've always been puzzled as to why there isn't a core perl5
> module with this functiona
On Oct 25, 2005, at 3:35 PM, Joshua Hoblitt wrote:
On Tue, Oct 25, 2005 at 06:31:43AM +0200, Fran?ois PERRAD wrote:
The subroutine check_progs defined in lib/Parrot/Configure/Step.pm
is not
portable (doesn't work on MSWin32).
On MSWin32, the real filename of a program is prog.exe, prog.
On Tue, Oct 25, 2005 at 06:31:43AM +0200, Fran?ois PERRAD wrote:
>
> The subroutine check_progs defined in lib/Parrot/Configure/Step.pm is not
> portable (doesn't work on MSWin32).
> On MSWin32, the real filename of a program is prog.exe, prog.com, prog.bat
> or prog.cmd , so if -x 'prog' is not
