Hi,
shouldn't UnixProcess>>unregisterChildProcess: removeKey: anOSProcess pid instead of: removeKey: self pid?
There are no senders of this message but at least with this change I can get rid of the instances of ExternalUnixOSProcess my problem from my other post.
Which still leaves the question if reusing one ExternalUnixOSProcess would be more appropriate.
Cheers,
Herbert
Hi Herbert,
Yes for sure, that is a bug. Thanks for finding it. I'll fix it as soon as I get home tonight.
Dave
Hi,
shouldn't UnixProcess>>unregisterChildProcess: removeKey: anOSProcess pid instead of: removeKey: self pid?
There are no senders of this message but at least with this change I can get rid of the instances of ExternalUnixOSProcess my problem from my other post.
Which still leaves the question if reusing one ExternalUnixOSProcess would be more appropriate.
Cheers,
Herbert
squeak-dev@lists.squeakfoundation.org