Re: Unloading Coercions
Re: Unloading Coercions
- Subject: Re: Unloading Coercions
- From: Richard 23 <email@hidden>
- Date: Thu, 22 Mar 2001 14:40:08 -0800
>
If after a reboot OSAXen that install coercions are removed from the
>
Scripting Additions folder and a script is recompiled, does that make the
>
script no longer use the coercions?
Yes...there is nothing special in the script that says "use this coercion"
which is what makes it particularly difficult to know whether a script is
only working because of custom coercion handlers. Until you run the
script
without those coercion handlers being available that is.
This would also mean that a recompilation is unnecessary...the coercions
no longer available would simply not be used.
As to the loading and unloading of handlers (event and coercion), I'd
recommend you read "About the OSAX Mechanism" in the AppleScript 1.3.4
SDK.
ftp://ftp.apple.com/developer/Development_Kits/AppleScript/Documentation/OS
AX/Scripting Additions Mechanism
>
Also, does there exist a method to determine what coercions an OSAX
>
installs?
Other than checking the osax resource of each scripting addition to see
which ones contain resources whose names start with CSDS or CSPT I'm not
aware of any. Of course standard additions doesn't have any osax items
in its resource fork, rather they would be contained in the data fork so
you're out of luck there. Fortunately there aren't any 3rd party osaxen
I'm aware of that use the "native scripting additions" method, nor has it
been officially endorsed by Apple.
Hope this helps and is mostly accurate!
R23