Beefy Boxes and Bandwidth Generously Provided by pair Networks
Come for the quick hacks, stay for the epiphanies.

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Ah, welcome aboard, wageslave!

To answer your question about $_, you can read that variable as "it". When you write something like print $_, you are saying "print it". You can, as you've discovered, leave the "it" out, and Perl will know what you mean.

As for the problems you're having in your three code snippets, here's a quote from perldoc -f eof to get us started:

eof FILEHANDLE eof () eof Returns 1 if the next read on FILEHANDLE will return end of file, or if FILEHANDLE is not open. FILEHANDLE may be an expression whose value gives the real filehandle. (Note that this function actually reads a character and then "ungetc"s it, so isn't very useful in an interactive context.) Do not read from a terminal file (or call "eof(FILEHANDLE)" on it) after end-of-file is reached. File types such as terminals may lose the end-of-file condition if you do.

What I'd like to point out from there is that eof is not a value, but rather a function. So when you do <STDIN>!=eof, you compare <STDIN> with either true or false. That's not something that's very printable, or something that makes a lot of sense. This is also why your second loop doesn't work.

Also, again from perldoc -f eof, I present the following snippet:

Practical hint: you almost never need to use "eof" in Perl, because the input operators typically return "undef" when they run out of data, or if there was an error.

Perl has a very practical view on what is true or false. When you do while (<STDIN>), you will stop when <STDIN> returns undef, which is considered false.

Keeping all of this in mind, here's how I might re-write your loop:

while (<STDIN>) { print; print "***\n"; }

Alternatively, I might write:

while (<STDIN>) { print $_, "***\n"; }

Good luck in your adventures!

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

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others lurking in the Monastery: (4)
As of 2023-12-06 21:08 GMT
Find Nodes?
    Voting Booth?
    What's your preferred 'use VERSION' for new CPAN modules in 2023?

    Results (32 votes). Check out past polls.