Re: Unloading Coercions
Re: Unloading Coercions
- Subject: Re: Unloading Coercions
- From: Chris Nebel <email@hidden>
- Date: Thu, 22 Mar 2001 16:26:00 -0800
- Organization: Apple Computer, Inc.
Richard 23 wrote:
>
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.
Native scripting additions have been officially endorsed since Mac OS 9.0 --
see Tech Note 1164 -- it's just that no one has bothered. I thought Smile had
a feature to track usage of scripting additions. Or does that only work for
commands, not coercions?
To answer the original question, 68K scripting additions (which currently
means everything other than Standard Additions, as far as I know) are rather
unpredictable about when they get unloaded. Depending on how memory gets
used, they can stick around well after you remove their files from the
Scripting Additions folder. The only way to be sure is to reboot.
--Chris Nebel
AppleScript Engineering