In article <a05200f00b9f976d5acfe@[63.120.19.221]>,
[EMAIL PROTECTED] (Dan Sugalski) wrote:
> Apparently there's a bug in Mac::AppleScript that needs fixing. OTOH,
> if there's nothing that Mac::AppleScript does that Mac::Carbon
> doesn't, then I'm all for tossing its guts and turning it into a
> simple wrapper for Mac::Carbon. No point in duplicating the code if
> there's no win.
I had thought of that, but I wasn't really sure what your plans were,
and didn't want to speak out of turn. If there is a need or desire for
both, fine; if not, then it makes sense to have only one. I'd not have
even bothered with DoAppleScript, except that it was a part of a module
I needed to port anyway (for SetFileInfo, GetFileInfo, Volumes,
MakePath, and MakeFSSpec), and I wanted to have a single codebase of
that module for MacPerl and Mac::Carbon.
So yeah, a simple wrapper would work:
use MacPerl 'DoAppleScript'; # no need to slurp in all of Mac::Carbon
*RunAppleScript = *DoAppleScript{CODE};
The only caveat is that right now Mac::Carbon is still in development
... and I am not entirely sure if there isn't any other significant
difference between the two functions.
--
Chris Nandor [EMAIL PROTECTED] http://pudge.net/
Open Source Development Network [EMAIL PROTECTED] http://osdn.com/
