I don't know why you think that would make any difference.
You'll notice that he doesn't say that using the oft-described method of setting non-blocking doesn't work, only that it works "for the wrong reasons".
That's okay. Just so long as it works!
His "proper way" is no such thing. It is at best a different way of working around the fact that the implementation of ioctl is broken.
There is no way that Perl programmer's should be messing around with pointers. pack 'p' (or is it pack 'P') is even more badly documented than ioctl and far, far too easy to get wrong and cause crashes.
The proper way would be to fix ioctl.
The limitation is in the Windows Tk implementation. Not Perl, nor Windows.
In reply to Re^5: Client/Server sockets with TK on Win32
by BrowserUk
in thread Client/Server sockets with TK on Win32
by merseyred
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |