Hi Blake, as I mentioned earlier, the designer of a native function can decide if she wants the corresponding shared library to be unloaded or not. I would claim that the designer of a library is in a better position to decide whether her library should be unloaded or not than the user of the library. Making this a user preference would cause more harm than benefits because all such a preference could achieve is additional errors in cases that would properly work when the preference is not set. If we would not )SAVE native functions then some workspaces, for example the FILE_IO workspace would no longer work, A )LOADed workspace could re-establish to-level native functions (but not, for example, localized native functions). A COPYed workspace could not even re-establish its native functions. That all sounds like something that you want to avoid in the first place. /// Jürgen On 11/11/2014 06:21 PM, Blake McBride
wrote:
|
- [Bug-apl] Shared library survives session Blake McBride
- Re: [Bug-apl] Shared library survives session Juergen Sauermann
- Re: [Bug-apl] Shared library survives session Blake McBride
- Re: [Bug-apl] Shared library survives sessi... Blake McBride
- Re: [Bug-apl] Shared library survives s... Juergen Sauermann
- Re: [Bug-apl] Shared library survi... Blake McBride
- Re: [Bug-apl] Shared library s... Elias Mårtenson
- Re: [Bug-apl] Shared libra... Blake McBride
- Re: [Bug-apl] Shared libra... Juergen Sauermann
- Re: [Bug-apl] Shared libra... Blake McBride