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 don't know what the status is currently, by I know that WxWindows should normally run well on OS X and that it supposedly has a very native look (it certainly does under KDE and win2k). WxPerl itself is a really nifty toolkit as well. Not to drag you away from what appears to be pleasureable coding in ObjC, but you might want to take a look at WxPerl.

    --

    -- Robin Berjon [berjon.com]

    • I have need of Cocoa support particularly, so WxPerl's not what I need. (Google can't find much mention of it, at least not OS X specific mention. The bits I can find are all very tentative)
  • I consider Carbon and Mac OS about as legacy as I consider perl 5. :-)

    However, yeah, Objective C is pretty darn cool in its flexible dynamic stuff. When doing Java shims for Cocoa they had to map out every little thing beforehand; not so for Perl!
    • Well, as the perl 6 gust sketcher (Now there's a good title for the business card), I do tend to look forward. Keep tripping over all these durned things in front of the horizon, though. :)

      I've half a mind to implement this for perl 6 at the same time as perl 5. That'd mean finishing the scratchpads, method call code, and AUTOLOAD. Not, mind, that this would be a bad idea...
  • I made this [perl.org] which made an Apple engineer give this response [develooper.com].

    :-)
    --

    -- ask bjoern hansen [askbjoernhansen.com], !try; do();