• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Results differ in editor and applet
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Results differ in editor and applet


  • Subject: Re: Results differ in editor and applet
  • From: has <email@hidden>
  • Date: Fri, 27 Feb 2004 15:34:01 +0000

Chris Espinosa wrote:

> 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.

Back then, *everything* hurt.<g> [1] Mind you, no reason the terminology resource format couldn't have been optimised to allow very fast retrieval of keyword<->AE code data (which is all the AS language uses), had this been necessary.

I'd guess the reason for pushing keyword-to-AE code conversion into the compilation phase would be more to streamline Apple event dispatching, as that's where constantly converting keywords to AE codes would really kill efficiency. This has the extra bonus of removing keyword conversion from execution altogether since AS (unlike most scripting languages) normally saves and loads scripts in compiled, not source, form. So, no reason for AppleScript's own engineers to optimise terminology retrieval and decoding as script editing and compiling isn't performance-critical.

For those that do have to fetch terminology at runtime though, is there anything that could be done to improve the OSAGetAppTerminology() bottleneck? [Happy to take this thread to AS-Implementors list, btw.]

Cheers,

has

[1] That said, a humble IIci probably slings around Word 5.1 easier than my G4/867 PB can Word X. Not too shabby for "buffer cache"... ;)
--
http://freespace.virgin.net/hamish.sanderson/
_______________________________________________
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.


  • Prev by Date: Re: Trigger script from remote machine?
  • Next by Date: Re: Trigger script from remote machine?
  • Previous by thread: Re: Results differ in editor and applet
  • Next by thread: AS/FMP: a list of fewer than two records
  • Index(es):
    • Date
    • Thread