• 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: Certain AppleScript failures under Leopard
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Certain AppleScript failures under Leopard


  • Subject: Re: Certain AppleScript failures under Leopard
  • From: Chris Espinosa <email@hidden>
  • Date: Sat, 01 Dec 2007 16:29:23 -0800

On Dec 1, 2007, at 4:19 PM, William Bates <email@hidden> wrote:

Under Leopard, I am running AppleScript 2.0.
Under Tiger, I am running AppleScript 1.10.7
I have certain scripts that work and have always worked well under Tiger, but fail under Leopard.
Is there a recommended way to do a backwards-compatible thing?

Well, remember that with Leopard all the apps are different, too, and Leopard has substantial differences in Cocoa Scripting support as well. So there's no pat answer for your question without seeing the script itself and the new failure you're seeing on Leopard.


Unless you're talking specifically about scripting Xcode, the cppledcript-users list might be a better place to getrhis question answered.

Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Certain AppleScript failures under Leopard (From: William Bates <email@hidden>)

  • Prev by Date: Certain AppleScript failures under Leopard
  • Next by Date: __attribute__((used)) not working in Xcode 3?
  • Previous by thread: Certain AppleScript failures under Leopard
  • Next by thread: __attribute__((used)) not working in Xcode 3?
  • Index(es):
    • Date
    • Thread