• 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: Multi-threaded - thanks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multi-threaded - thanks


  • Subject: Re: Multi-threaded - thanks
  • From: Bill Briggs <email@hidden>
  • Date: Fri, 7 Nov 2003 11:59:15 -0400

At 10:43 PM +1100 07/11/03, Shane Stanley wrote:
On Nov 7, 2003, at 10:22 PM, Bill Briggs wrote:

At 10:28 PM -0600 06/11/03, John C. Welch wrote:
On 11/6/03 10:05 PM, "Bill Briggs" <email@hidden> wrote:

Thanks for the multi-threaded AppleScript in Panther. :-)

What? Where in the release notes is this????

I didn't read it in the release notes. I did what I do with every new release of AppleScript, I tried it. Ran two scripts that don't have a chance to get in the way of each other, each of which takes half a minute to run, and they both run simultaneously and return the expected result. It's the first time I've been able to even get two scripts to run at the same time. Now I've got some whacky fun to have with this getting two scripts to do battle with each other.

I think what you're seeing is the (documented) change from LIFO to FIFO processing. Nice, but not really multi-threading.

I haven't read the release notes - yet - but from an OS perspective as far as I understand it, the difference between LIFO and FIFO is precisely the difference between non-preemptive thread scheduling and preemptive thread scheduling. In the case of FIFO you are able to run simultaneous threads. LIFO blocks pending thread execution because it can't pre-empt the running thread, effectively rendering it a single thread system.

Whether or not the thread scheduling here is being managed at the kernel level (probably what you mean by multithreading) or the user application level (just restricts threads to the application's memory space, which they have to share) I don't know. I suspect it's the user application level here. The user effect is pretty obvious, and probably wouldn't look a lot different no matter which entity managed the thread scheduling. Before you couldn't even click in a second Script Editor window to run a script. The system just beeped at you. Now you can actually run a second thread at the same time as the first.

If I have this wrong maybe Chris N. will clarify.

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

  • Follow-Ups:
    • Re: Multi-threaded - thanks
      • From: Christopher Nebel <email@hidden>
References: 
 >Re: Multi-threaded - thanks (From: "John C. Welch" <email@hidden>)
 >Re: Multi-threaded - thanks (From: Bill Briggs <email@hidden>)
 >Re: Multi-threaded - thanks (From: Shane Stanley <email@hidden>)

  • Prev by Date: applescript-users digest, Vol 3 #2138 - 18 msgs ( -Reply)
  • Next by Date: Re: AppleScript Studio and Filemaker
  • Previous by thread: Re: Multi-threaded - thanks
  • Next by thread: Re: Multi-threaded - thanks
  • Index(es):
    • Date
    • Thread