Re: Results differ in editor and applet
Re: Results differ in editor and applet
- Subject: Re: Results differ in editor and applet
- From: Paul Berkowitz <email@hidden>
- Date: Thu, 26 Feb 2004 21:59:52 -0800
On 2/26/04 9:32 PM, "Chris Espinosa" <email@hidden> wrote:
>
On Feb 26, 2004, at 4:25 PM, has wrote:
>
>
>
>> Because the AppleScript runtime (the part that runs the scripts)
>
>> doesn't want to invest the extra time in loading all the information
>
>> that's needed in order to compile and syntax-check scripts if it's not
>
>> necessary.
>
>
>
> Based on my own experience, I'd add that parsing a terminology
>
> resource is a fairly simple operation, taking a trivial (i.e.
>
> unnoticeable) amount of time on modern Macs.
>
>
Of course this is true, with your dual 1.2MHz G5 processors with a gig
>
of RAM.
>
>
The architectural decision to do this was made when the top-of-the-line
>
machine was a Mac IIci with 32Mb of memory. (That's a decent buffer
>
cache nowadays).
>
>
Back then, loading terminology hurt. Bad.
So, nowadays, the 'run script' method is the easiest and simplest to do,
with no perceptible toll if done just once per script. The 'if theClass is
string then set theClass to "string" else if...' etc stuff can get rather
tedious if there are 35 different classes (or other types) to check,
although I use it myself for 5 or so.
How does 'run script "tell application \"some app\" \r end tell"' force the
app's dictionary to load?
--
Paul Berkowitz
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.