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

use Perl Log In

Log In

[ Create a new account ]

brian_d_foy (44)

brian_d_foy
  brian.d.foy@gmail.com
http://www.pair.com/~comdog/

Journal of brian_d_foy (44)

Sunday September 02, 2007
06:36 PM

ActivePerl is almost everywhere now

[ #34317 ]

The Gecko isn't just for Windows anymore.

I must have missed the news from ActiveState that ActivePerl now runs on Mac OS X. Actually, it's now on Windows, Linux, Solaris, HP-UX, and AIX too. I guess I should have figured ActivePerl had made it to the Mac when Komodo did, but I never thought to actually use it. Maybe I know about it when it happened, then just forgot.

I've now installed it, and I see that it comes with the Mac::Carbon and Mac::Glue module, along with a lot of other Mac::* stuff. Very cool.

I'll have to wait to play with it. I was just checking some facts for a Komodo article in the next issue of The Perl Review , so I can't get too distracted right now.

And hey, AIX but no FreeBSD? :)


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

ActivePerl is almost everywhere now 7 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • ActivePerl was there long before Komodo was.
  • There's a certain irony to the Mac version of the PPM library being the most complete and having the highest CPAN coverage, while the Win32 version of ActivePerl has by far the worst CPAN coverage.

    • Certainly somewhat ironic, but there is also a purely technical reason. To provide forward binary compatible PPM packages, the PPM system is building it's packages using as close to the earliest ActivePerl available on that platform as possible.

      That means ActivePerl 813 (5.8.7) for OS X, and ActivePerl 806 (5.8.0) on Win32.

      It also explains the better CPAN coverage (5.8.0 vs. 5.8.7)

      --
      There's more than 9 ways to do it
      • That's not a technical reason, that's a business reason.

        Sacrificing most the usful modules on CPAN to maintain backwards with 5-10 year old legacy version of Perl for what I assume is contractual reasons (correct me if I'm wrong here) is hardly a technical decision, or if it is, it's a bad technical decision.

        On ActivePerl Win32 you end up with.

        No PPI, or anything that uses it.

        No POE, or anything that uses it.

        No WWW::Mechanize, or anything that uses it.

        No Params::Util (so there goes almost everything I've wr
  • Not to diss the fine work of the ActiveState people, but perl is already very well integrated in FreeBSD : in the 4.x branch Perl 5 was in the base system and was a key component for many admin scripts. There are 5000+ CPAN modules mostly up-to-date that can be installed in one command ('portinstall p5-*' but don't do that), and even if it's not perfect the BSDPAN module is a life-saver.

    Furthermore, free beer coupon to the first one who can name that revolutionary feature the packager added in FreeBSD and y
    • Indeed, kudos to FreeBSD, who currently hold by a wide margin the record for the best and most current CPAN coverage.
  • Yeah, I'd say you missed it. ActivePerl for Mac OS X was released in June - of 2005. :-)

    http://www.mail-archive.com/macosx@perl.org/msg08584.html [mail-archive.com]
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.