comment on

> A: <STDIN> is returning a newline character '\n', which
> is true. In practice, regardless of O/S, you never get
> the empty string or a bare 0, hence the only false value
> you encounter is undef.

I think, the construct while (<STDIN>) { is just another way to write: while (defined ($_ = <STDIN>)){, not only for while ($_ = <STDIN>) {.

The difference is not big; only if there is a 0 (=zero) on the last line of a file without \n, it can become essential. But with pure STDIN this case might never happen, only with files or the like...

Best regards,
perl -le "s==*F=e=>y~\*martinF~stronat~=>s~[^\w]~~g=>chop,print"

In reply to Re: Re: Re: question about $_ and eof by strat
in thread question about $_ and eof by wageslave

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.


P is for Practical
	PerlMonks