Just as an aside, killing or suspending threads other than your own is dangerous and probably shouldn't be done, anyway.
I agree that playing with Processes is a good way to screw up ones system UNLESS one really knows what they are doing and is VERY careful to use Processes safely.
I've been programming with Processes in Smalltalk for over a decade and I'm VERY careful to use them properly.
So in short, it doesn't look like this is a bug that seriously needs fixing.....
You don't think that two bugs in one of the kernel objects (the most relied-upon objects in the system) is worth fixing? Even when the methods clearly do not do what their comments say they are supposed to do?
You wouldn't even amend the comments to note that the implementation has bugs and what they are?
You must work for Microsoft. :-)
:-) Carl
You wouldn't even amend the comments to note that the implementation has bugs and what they are?
To quote another message from the other day:
Hear, hear! Alan, via Dan, puts very well the old OSS mantra: "you said it, you do it." While we all work furiously on various projects, and suggestions and tweaks are always invited, the single best solution is the Nike slogan.
You seem quite competent in this subject. Basically transform your postings in the proper method comments and post them. Don't forget a subject tag like. [FIX (not really)] or something.
Best regards, Henrik
< = > .
squeak-dev@lists.squeakfoundation.org