Re: Keydata question

[David Sugar]

Keydata is derived from a "mempager" class.  The mempager can accululate 
memory allocations thru paged blocks which are then doled out into smaller 
objects as nessisary without additional memory allocationc calls.  Mempager 
releases all allocated memory blocks when it is destroyed (or Purge is called).

To answer your question more specifically, your SIGHUP handler should 
"Purge()" the current keydata, and then "Load()" new config info, as this is 
more efficient than destroying and created a new keydata object.

Paul Marculescu wrote:

> Hello!
>
> If I use Keydata in a deamon, to read its configuration, and I want to
> register the SIGHUP signal, so the daemon gets reconfigured when it
> receives this signal, how should the Keydata act when there is need to
> release current configuration?
>
> What happens with the keysym_t structures that are allocated every time
> a getLast() ( for example ) is called? Where does that memory get freed,
> as I cannot find any free() call for that?
>
> Thanks.
>
> --
> Paul Marculescu
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp