welcome back Harald
I probably blundered my goal with my message to the Tcl core list.
Gustav answered telling the whole story of what a fork is. I know what a
fork is. I did not insist though, sometime the dialog between Alexandre
and Gustav was dense and for a while looked like was about to take a
stubborn attitude, so I didn't want to add a third voice. I'm still
concerned that we might run into troubles, Gustav clearly doesn't like
fork at all and he's been pushing a solution fork-agnostic. I hope the
trade off they found will square away every problem. OTOH for example we
were very wise when we recommended not to leave I/O channels open when a
ServerInitScript terminates.
I don't know what the guys at FA think of it, but if they still use the
feature of interpreter cloning across a fork call I recommend they stay
tuned on the core list to understand what happens
cheers
-- Massimo
On 17-08-2015 13:24, Harald Oehlmann wrote:
Massimo,
thank you careing and answering on the tcl core list.
The lazy handling was discussed before. TCL is using that on the MAC
with a list of around 100 open bug tickets ;-)
It meight happen, that the notifier may work after the fork, as the
fileevent command will automatically check if there is a notifier
thread. If not (which is the case after the fork) it is started.
The discussions between Alexandre and Gustav are much to complicated
to me, as it was two years ago already ;-)
I recommend to stay a bit quiet and observe what happens.
I am back from holidays by the way ;-)
Regards to the team,
Harald
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
