in reply to Re: Sockets, ioctl and non-blocking reading on ActivePerl
in thread Sockets, ioctl and non-blocking reading on ActivePerl

dam... so simple, I don't know how I missed it. Many, many thanks!

I'm guessing the reason why is that the OS needs a reference to a string containing a non-zero value, and not an actual integer.

(incidentally I had also tried \1 thinking it was the same thing, but this complained that Can't coerce readonly REF to string... It makes much more sense now.)