comment on

The ugly part of Alertable IO is that you will always read (at least) one byte that you can't easily stuff back.

For files, it essentially mean buffering the input within the application. Select for unix must do the same thing, though the buffering is probably done by the OS rather than in user space. For files, 'put back' simply means a negative seek.

For pipes, the data has to have been received and therefore buffered before any OS can tell it it can read. PeekNamedPipe() just allows to to find out how much (and what, but that's by the by) has been received and buffered.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

In reply to Re^5: [Win32] IO::Select's can_read method by BrowserUk
in thread [Win32] IO::Select's can_read method by syphilis

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl Monk, Perl Meditation
	PerlMonks