On Apr 5, 2013, at 12:24 PM, Nick Kew wrote:
>
> On 5 Apr 2013, at 18:53, James Peach wrote:
>
>> Ah. It seems dangerous to me; some other plugin could register a subsequent
>> atexit() that depends on the DSOs that you are tearing down.
>
> To depend on a library, would it not have to take p
On 5 Apr 2013, at 18:53, James Peach wrote:
> Ah. It seems dangerous to me; some other plugin could register a subsequent
> atexit() that depends on the DSOs that you are tearing down.
To depend on a library, would it not have to take place after the library is
loaded?
In which case, its atexi
On Apr 5, 2013, at 10:24 AM, Nick Kew wrote:
> On Fri, 05 Apr 2013 09:10:47 -0700
> James Peach wrote:
>
>> BTW, why does it bother trying to unload the libraries?
>
> A sense of tidiness and order?
Ah. It seems dangerous to me; some other plugin could register a subsequent
atexit() that dep
On Fri, 05 Apr 2013 09:10:47 -0700
James Peach wrote:
> BTW, why does it bother trying to unload the libraries?
A sense of tidiness and order?
There's precious little in my life, but it's Good Practice
in software, IMHO.
--
Nick Kew
On Apr 5, 2013, at 3:13 AM, Nick Kew wrote:
> Igor pinged me a couple of days ago about libloader, the tiny
> plugin that serves to load libraries (in the manner of LoadFile
> in HTTPD). He also tweeted Qualys.
>
> Since then I've exchanged email with Brian, and he's happy to
> donate it. If f
