Re: use vs. Scripting Additions
Re: use vs. Scripting Additions
- Subject: Re: use vs. Scripting Additions
- From: Shane Stanley <email@hidden>
- Date: Mon, 30 May 2016 09:40:08 +1000
On 29 May 2016, at 9:13 AM, Mitchell L Model <email@hidden> wrote:
>
> it turns out (10.10 and later) that once you have a “use” statement, the any Scripting Additions — Standard Additions in particular — will not get loaded unless you include
> use scripting additions
> in your script.
FYI, that actually happens from 10.9.
> I don’t see any reason not to do that, especially as you are transitioning to using “use”, because there’s a lot in Standard Additions that you are so used to using that you may not realize they aren’t in AppleScript per se.
In general, I'd agree. But for people who use a lot of scripting additions, or keep old additions hanging around, there's a lot to be said for leaving it out, and adding "use terms from scripting additions" blocks where necessary. That helps reduce the risk of terminology conflicts, and also eliminates problems with some older additions' coercions.
--
Shane Stanley <email@hidden>
<www.macosxautomation.com/applescript/apps/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden