Re^2: poorly documented behaviour of readline() and IO::Select

Anyway. I wish "fix" this somehow in perl distribution. I.e. fix perl documentation.

Write note that "select/can_read indeed can return nothing when you actually can read"

Do you think that would be possible ? How to do this ? Use http://rt.perl.org/perlbug/ ?

Comment on Re^2: poorly documented behaviour of readline() and IO::Select

Replies are listed 'Best First'.
Re^3: poorly documented behaviour of readline() and IO::Select by ikegami (Patriarch) on Apr 28, 2010 at 23:33 UTC
Currently, the documentation for `select` says WARNING: One should not attempt to mix buffered I/O (like `read` or `<FH>`) with `select`, except as permitted by POSIX, and even then only on POSIX systems. You have to use `sysread` instead. This should be present in the documentation for IO::Select as well. (I wonder what exceptions POSIX makes, and if they are still applicable to Perl.)	[reply] [d/l] [select]
Re^4: poorly documented behaviour of readline() and IO::Select by vsespb (Chaplain) on Apr 29, 2010 at 14:17 UTC
yes, it does not seem to present in IO::Select. also as I told above eof() cant be used too!	[reply]
Re^5: poorly documented behaviour of readline() and IO::Select by ikegami (Patriarch) on Apr 29, 2010 at 18:22 UTC
The following builtins perform buffered reading: `read` `getc` `readline` (aka `<>`) `eof` `readpipe` (aka backticks) probably does as well, but it's not relevant here since it doesn't operate on a file handle.	[reply] [d/l]
Re^3: poorly documented behaviour of readline() and IO::Select by BrowserUk (Patriarch) on Apr 28, 2010 at 13:39 UTC
Try typing 'perlbug' on your shell command line.	[reply]


good chemistry is complicated, and a little bit messy -LW
	PerlMonks