Re: AppleScript in Rosetta
Re: AppleScript in Rosetta
- Subject: Re: AppleScript in Rosetta
- From: Paul Berkowitz <email@hidden>
- Date: Wed, 13 Sep 2006 10:17:59 -0700
- Thread-topic: AppleScript in Rosetta
On 9/13/06 1:41 AM, "Christopher Nebel" <email@hidden> wrote:
> I thought we'd hashed this out when the Intel Macs were introduced.
> Essentially, Rosetta-ed (emulated) processes are slower than
> equivalent native processes. (Emulation does cost, after all.)
> Therefore, you'll see a slowdown proportional to the amount of code
> that you're running in emulation.
>
> Where this gets tricky for scripts is that whenever you tell some
> other application to do something, it's *that* application's native-vs-
> emulated status that matters, not yours. Therefore, if you tell an
> emulated application -- say, Entourage -- to do something huge, it
> won't make any difference whether or your script is saved Universal or
> not. (Well, that's not quite true. If the amount of data coming back
> to your script is really large, then it'll pay for your script to be
> native, because that data gets handled in your process. However, that
> happens after the event reply comes back, and therefore isn't subject
> to timeouts.)
Thanks, Chris. That's what I figured, but wanted to make sure.
>
> The first thing I'd check is, if you boost the timeout for this case,
> does it eventually come back with the correct answer? Entourage may
> just be completely gagging.
That's what I figure too. The command is
get every contact whose modification date > someDate
and it's in a 10-minute timeout. I can't imagine that giving it more than 10
minutes is going to make any difference.
--
Paul Berkowitz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden