NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
next version (Score:1)
Re: (Score:1)
I don't think autobox still requires a perl patch actually, here is an excerpt from the changelog
- Stevan
autobox (Score:1)
Re: (Score:1)
So I assume it will appear when 5.10.1 arrives.
Installing into locations other than C:\strawberry (Score:1)
I still don't see where the difficulty is [perl.org]. You can skip the "Set up $ENV{PATH}" step in the setup for other locations (like, say, C:\Program Files\Strawberry Perl) and supply a batch file that sets up a "Perl Console" which has the correct $ENV{PATH}:
Re:Installing into other locations (Score:1)
vote++
Re:Installing into locations other than C:\strawbe (Score:1)
2. CPAN.pm and another config file have specific paths (I've made a path-agnostic CPAN.pm for the next release as a first stage).
3. I refuse to limit people to only be able to have working Perl applications if they launch a "Perl Console".
Perl apps should Just Work, regardless of how you run them.
If I do Start... Run... perlapplication, and it fails, it's not good enough.
I'm sure there's a better solution that DOE
Re: (Score:1)
The Win32 Makefile does not enable relocation by default because Perl has always been relocatable on Win32. It's only some modules that aren't without some patching. I've used Perl since 5.6 on Windows in various directories and never encountered any problem that wasn't related to badly written Perl modules that couldn't cope with whitespace in directories.
Double-clicking any Perl program will work even if Perl is not in $ENV{PATH} on Windows, because you (presumably) set up the file association between th
I refuse to limit people... (Score:1)
Re: (Score:1)