Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I just installed XP under Parallels last night to do win32 perl testing, and installed SP again. Thank god for Strawberry Perl.
  • There might be a URL typo. I clicked the link for http://vanillaperl.org/ [vanillaperl.org] and received a not found. A Google search for strawberry perl revealed http://vanillaperl.com/ [vanillaperl.com] instead.

    I look forward to trying Strawberry out. I usually have to cross develop under Cygwin.

    Later, Mark S.

    BTW, Thanks for the Tiny Modules too. Can I also cast a vote for a Tiny JSON module?
  • I've mentioned this in some emails when asked about Vanilla and Strawberry Perl, but it probably is worth repeating here...

    Strawberry Perl has led to a substantial shift for many people from installing modules in PPM form to installing directly from CPAN. That means that a lot more test suites are being run on MSWin32 and a lot more bugs are seeing the light of day.

    Much of the energy of project participants in the last year or so has been going to gradually squashing these bugs. You can see some of t

    • David,

      May I put in a request for a 5.10 version of Strawberry Perl, even though it's not yet released? Or otherwise, how can the kids try this at home?

      What do I need, over and above the blead source, to compile it and produce my own, say, Mango Perl on Win32?

      • At the moment you need to wait for a little bit for me to get the refactor of Perl::Dist finished, as there's no sane way to build atm... but that shouldn't be too far away.
  • Not true.

    I'd say that the Strawberry Perl distro is much better than ActiveState (I almost said "vastly", but that would be unfair).

    AS is bearable if you have Visual Studio installed, and know a few extra PPM repos that you routinely set up on new machines.

    But when I tried out Vanilla and Strawberry Perl I was pleasantly surprised. Things just... worked! I had less problems installing some things on Windows than on Ubuntu (how. about. that!).

    If this experience can be verified by other Windows users (and I
    • My actual subject was "Strawberry > ActiveState", but that got clobbered somehow...
      • It's a "bug" (pudge may not actually consider it a bug).

        SlashCode does not escape comment headers.
    • The main reason we kept the label on was that I wanted to be really conservative with a distribution.
    • The thing is, if you have pure-Win32 programmers that never touch Unix, they tend to be using Visual Studio and so on already. They have a familiarity with Visual Studio and the Win32 ways of working,

      In this environment, the better and less confusing environment for them does seem to be ActiveState.
      • I've found the opposite. I use Visual Studio.NET at $work, all day, every day so I'd consider that being a pure win32 programmer. But that's now in the age of .NET, where you don't have to know a lick of C to do real things, like http modules, services, etc.

        Back in the Visual Studio 6 days, one could compile a perl module [mod_perl.. oi] even if you didn't know C [as painful as it may have been to get studio to play along], and you could be fairly certain that the modules would work just fine.

        When .NET 1.0,