[Pharo-project] #& in Socket >> #waitForSendDoneFor:

Schwab,Wilhelm K bschwab at anest.ufl.edu
Tue Nov 9 22:47:18 CET 2010


The *possible* connection is that pushing limits has a way of making otherwise benign problems show themselves.


From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Philippe Marschall [kustos at gmx.net]
Sent: Tuesday, November 09, 2010 2:21 PM
To: pharo-project at lists.gforge.inria.fr
Subject: Re: [Pharo-project] #& in Socket >> #waitForSendDoneFor:

> IMHO, the socket should do what it is asked to do, blocking only the calling thread, and let other threads and/or the user decide when that is taking too long.

What does this have to do with replacing a #& with a #and:?

> Could you be getting timeouts that are causing unexpected behavior?

I don't think so, see above. Since I can't reproduce it anymore it was
probably a measuring inaccuracy (~3 %). However I think it's still
worthwhile replacing that #&.


More information about the Pharo-project mailing list