• 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: hash arrays and other mysteries
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: hash arrays and other mysteries


  • Subject: Re: hash arrays and other mysteries
  • From: Jon Pugh <email@hidden>
  • Date: Fri, 19 Oct 2001 10:29:39 -0700

At 4:23 PM +0100 10/19/2001, has wrote:
>I can understand that compiling a string as executable code takes a certain
>amount of time, and that doing this during runtime has implications for the
>"parent" script's speed. Except Smile's "do script" does the same thing,
>but in a fraction of the time. I don't understand why. Maybe Smile has its
>own built-in compiler that happens to be faster than Applescript's own? Or
>some other reason?

He's preloaded the compiler. With "run script" it's a one shot, so it has to load, compile, execute and unload everything. Any running app, like script editors, can keep an instance of the compiler loaded, so that all they have to do is compile and run. No loading and unloading. It takes more memory and an app to keep stuff around, but it works much faster.

Jon


References: 
 >Re: hash arrays and other mysteries (From: has <email@hidden>)

  • Prev by Date: Deselecting items of the desktop
  • Next by Date: Re: Converting an applescript from 68k app to PPC
  • Previous by thread: Re: hash arrays and other mysteries
  • Next by thread: Re: hash arrays and other mysteries
  • Index(es):
    • Date
    • Thread