🚀 go-pugleaf

In Article <15034265wnr@thermoteknix.co.uk> David Wood  writes:
>Hello one and all

Hi,

[snip]

I think you might find it's a problem in your coding.  And especially 
in the coding of your tcp/ip class.

I have a class library that does much the same thing.  There's a socket
class and which contains and embedded window.  The window has an extra
window long which stores the this pointer.  When you get an fd* message
you pick up the window long, cast it into a socket pointer and then
call the virtual Read or Write call or something.  You have to be super
careful not to call the socket destructor during any of these calls because
clearly that's going to screw you up because you've got to unwind back 
the stack through the windows procedure.

It's really really easy to make mistakes with this when you have lots
of derived classes and virtual function calls.  For what it's worth,
I call closesocket in response to fd reads or fd accepts all the time and
the system doesn't hang.

--E.