Ok, I will open the bug. I didn't mean it bad, I just only wanted to know
if it isn't inappropriate to post about bug in mailinglist.
Jan
Can you open a bug entry with code showing the problem?
Now this is not that we do not care but we are busy taking care of family,
team, business…..
Stef
On Jan 14, 2012, at 10:34 PM, Garret Raziel wrote:
> Hi, I think I found bug in pharo image. I would post it in bug tracker
> but I don't
I see the problem but I wouldn't know who's responsible.
ConnectionQueue>>listeLoop contains the following line:
newConnection := socket waitForConnectionFor: 10
"newConnection" is later sent the message #isConnected. The problem is that
Socket>>waitForConnectionFor: answers "true" and not a co
??
What is your email about?
Alexandre
On 15 Jan 2012, at 11:51, Garret Raziel wrote:
> Anyone cares?
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Anyone cares?
Hi, I think I found bug in pharo image. I would post it in bug tracker
but I don't know if it is not duplicate to this bug
http://code.google.com/p/pharo/issues/detail?id=3349&can=1&q=ConnectionQueue&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty.
If you create ConnectionQueue to lis
