Performance: fhandler_socket and ready_for_read()
Wed Jul 31 02:53:00 GMT 2002
On Tue, Jul 30, 2002 at 10:02:13PM -0400, Chris Faylor wrote:
> Now that you mention it, though, this could be handled (correctly?) by
> calling set_r_no_interrupt whenever we first create a socket iff
> winsock2_active. I think putting this in the fdsock function would
> catch this. This means that I didn't have to virtualize this method.
I agree. Just setting the flag is cleaner than overriding the method
while the flag is still set to a wrong value, isn't it?
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:firstname.lastname@example.org
Red Hat, Inc.
More information about the Cygwin-patches