develooper Front page | perl.module-authors | Postings from July 2011

Re: Quick and dirty guide to running Perl on Windows (was Re: Makingsure your module works on other OS-es as well)

Thread Previous
From:
Serguei Trouchelle
Date:
July 9, 2011 01:38
Subject:
Re: Quick and dirty guide to running Perl on Windows (was Re: Makingsure your module works on other OS-es as well)
Message ID:
4E181378.7000908@cpan.org
Eric Wilhelm wrote:

> With a VM install, you still have to wade through the boggy experience
> of mousing-around in a completely foreign environment while swearing at
> the shell for being completely unreasonable about everything.

I know that Norton Commander clones generally are not used anywhere outside the former Soviet Union, but you may take a 
look at Far Commander ( http://www.farmanager.com/download.php?l=en ) and install MSYS and MinGW (and optionally: 1. 
install ActivePerl, 2. Install StrawberryPerl).
After that, you should have something close to your working environment, and more (thanks to Far Cmdr).

> It seems like you could construct a pretty thoroughly windowsish
> environment by hiding all useful commands (e.g. rename /bin,/usr/bin)
> and unsetting $PATH, then make some working/temp directories with
> spaces in the names.  That would catch most of the common problems.
> Not sure if you could emulate the brokenness of the backslashes on a
> *nix though.

Perl on Windows doesn't have any problems with straight slashes. Unless you do my $bla = `/bin/sh`;
Something like "open (my $FILE, '<', '/Windows/TEMP/File.txt')" works just fine, though I would recommend using 
File::Spec->cat just to be sure.

P.S. Programming in Perl on the Windows as primary platform for more than 10 years.

-- 
Serguei Trouchelle

Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About