Re: Identify conflicts! Re: AppleScript a miserable and utter failure
Re: Identify conflicts! Re: AppleScript a miserable and utter failure
- Subject: Re: Identify conflicts! Re: AppleScript a miserable and utter failure
- From: has <email@hidden>
- Date: Wed, 28 Sep 2005 23:57:13 +0100
Don Briggs wrote:
>>My take on the fuss is simply that there needs to be a language czar who ensures that terminology conflicts are fixed.
>I nominate Script Editor as the authority charged with identifying such terminology conflicts.
>To me, it seems reasonable to expect Script Editor to warn us of conflicts, especially at "Compile" time.
>Am I wrong?
Yup. SE plays no part in script compilation. Compiler warnings would need to be emitted by the AppleScript component. Apple would probably need to extend the OSA API to support this, and OSA editors could then adopt this as they wanted.
Alternatively, if someone really wanted, they could write a tool that inventorizes all installed osaxen on a user's system, and checks for potential conflicts between those and selected applications. Wouldn't be that hard (most of the code you'd need I've already written and released as open source).
has
--
http://freespace.virgin.net/hamish.sanderson/
_______________________________________________
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