Slash Boxes
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Let us not shun the Win32 programmer ...

    I'd disagree that the installation is poor with ActivePerl, as you can run 'ppm' and 'cpan' pretty much from the off. Admittedly you are relying on a largely non-current repository away from CPAN, but it is a start. Having a reliable codebase from which you can install from is the key part. There are several of us who program on Windows and have to either patch CPAN modules ourselves, try alternatives or rewrite the code. I'd rather see more effort being put into

    • Is it any wonder why ActiveState's repository is so far behind?

      Considering the number of bug reports they've sent for my modules... no. I'd love to have more feedback.

      • That's a fair point. I wish they did send their reports. Although at least they are available online, just about.

        In several cases there are CPAN Testers reports that match the test problems ActiveState have. However, looking at the reports generated for your modules I noticed many of the problems are missing because of the way Module::Build tests are not currently passed back to CPANPLUS. This is someting that is being looked at.

    • It's the centrally run largely outdated non-CPAN repository that causes much of the problem. Instead of working out how to get a proper compiler working inside a default install of a Windows version of Perl, we have what is an enourmous workaround.

      Is PXPerl does nothing else but solve the nmake/compiler problem on Win32, it will be a huge success, and we can look at dealing with module-problems from there (and be able to actually test things outself).

  • Excellent post. Thanks!