Hi Kay,
hmm, your proposal looks more like a concept rather than an API proposal .
Will there be an API somewhere in sal for this ? If yes, I would rather
see the API docs before actually putting comments.
I can't see how your concept should work work for daemon threads, when
shared libraries are dynamically loaded. From "man atexit"
--snip--
The atexit() function registers the given function to be called at
normal program termination, either via exit(3) or via return from the
program's main(). Functions so registered are called in the reverse
order of their registration; no arguments are passed.
--snap--
. AFAIK, the static destructors of objects in shared libraries are
called by atexit functions, arent they ? So your daemon_join_ would be
called too late.
I'd rather prefer an explicit daemon_join in main() to avoid those kind
of problems ...
Bye,
Joerg
Kay Ramme - Sun Germany - Hamburg wrote:
Hi again,
if no one objects, this is going to become the standards policy
regarding thread life cycles soon.
First thing I am going to change accordingly is the pyuno bridge ...
Kay
Kay Ramme - Sun Germany - Hamburg wrote:
Hi OOo developers,
once a while we face the situation, that it is unclear how a long a
thread should live, if it should be cancellable, and when the
containing process is going to terminate (e.g.
http://udk.openoffice.org/issues/show_bug.cgi?id=80300).
Therefor I wrote a short proposal about controlling the life time,
supplemented by some example code to illustrate the behavior.
If you are interested, please have a look at
http://wiki.services.openoffice.org/wiki/User:Kr/A_Thread%27s_Life
and comment on the discussion page.
Ideally the proposal becomes a specification, being mandatory for
thread implementors.
Thanks for your help and feedback
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
