MacPerl 5.6.1 Released

pudge (apple.slashdot.org editor and MacPerl Maintainer) writes "MacPerl 5.6.1r1 is the first release of MacPerl in four years. It is now based on perl 5.6.1 -- actually on the latest unreleased 5.6 sources, so MacPerl is the most advanced release of perl ever -- and support for MacPerl is now in the perl core, for both 5.6 and 5.8. MacPerl can also be built entirely with freely available software. And, like its predecessor, it runs on Mac OS X under the Classic environment. Read the announcement, and see macperldelta for details on what's changed."

Comments

Why the hell would you run it under Classic?

[Anonymous Coward]

MacPerl may be needed for pre-X Mac OS, but what's the point of running a port of perl to a legacy environment? The "real" perl runs on Mac OS X without any porting. Why anyone would waste time and resources running it under Classic is beyond me.

Re:Why the hell would you run it under Classic?

[pudge]

Actually, no sir: I answered the spirit of the question precisely. You are asking a separate question, which is why I, personally, spent time MAKING MacPerl. As to that, I can only say that it is odd that you would presume to have a reasonable opinion of what is the best use of my own time and efforts, since you, of course, cannot. :-) Suffice it to say that it is more than worth the time and effort, as a point of fact, regardless of your opinion on the matter.

As to Carbon/Cocoa bindings for Mac OS X: they are in progress. But they are irrespective of MacPerl, except that they will, eventually, obviate the need for MacPerl on Mac OS X, and the Carbon bindings will likely work on both Mac OS and Mac OS X.

Re:Why the hell would you run it under Classic?

[Anonymous Coward]

Why anyone would waste time and resources running it under Classic is beyond me.

Yes. We know. It's a guardian rule of Macintosh computing that we must immediately forsake any one-generation-old version and immediately pitch it all into the landfill.

Is this relevant?

[AutumnLeaf]

How relevant is this? I found the inability to fork subprocesses, and the general "anti-command-line" tendencies of applications on the Mac OS, to make Mac Perl's usefullness much diminished compared to traditional unix environments. In many respects, I think AppleScript is the more effective scripting language for the classic Mac OS, although certainly it's not as fun or easy to work with as Perl (speaking from experience someone who's worked with both.)

Does anyone out there actually use Mac Perl for major development?

Re: Is this relevant?

[inkswamp]

How relevant is this?

In 50 words or less: quite.

I found the inability to fork subprocesses, and the general "anti-command-line" tendencies of applications on the Mac OS, to make Mac Perl's usefullness much diminished compared to traditional unix environments.

Nothing personal but this sentiment just reeks of Geek Tunnel-vision. MacPerl is possibly one of the most powerful, useful tools on the Mac that I have at my disposal in running my company's website. I can't imagine what I'd do without it. Because it doesn't support a few (IMO) esoteric technical issues hardly diminishes its relevance.

Bear in mind that there are Mac-specific libraries distrbuted with MacPerl that interface with the Mac API/Toolbox (I was awestruck when I got my MacPerl script to access the Speech Manager--a talking Perl script. Cool!) Does the lack of those libraries on Unix diminish its usefulness there? I doubt it.

In many respects, I think AppleScript is the more effective scripting language for the classic Mac OS, although certainly it's not as fun or easy to work with as Perl (speaking from experience someone who's worked with both.)

I can speak as someone who's worked with both as well and I find that they naturally lend themselves to different tasks. If you want the ability to manipulate raw data or sift through enormous quantities of information, Perl is hands-down the way to go. If you need a quick script to facilitate interapplication communication, exchange of data between apps, or to automate a program (and especially if you need an application that can communicate with non-geek users via GUI elements) AppleScript is hard to beat since that functionality is built right in, no loading extra libraries which makes for quick and lean scripts. Each has its own strength. I don't think I've ever been in a quandry over which one to use for any given task.

Does anyone out there actually use Mac Perl for major development?

Probably not, but how does that diminish its relevance to those of us who leverage its power on a daily basis to conquer some Herculean tasks? I find this update unexpected, exciting and quite relevant..

--Rick