Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I'm a big fan of the "you should go read the docs" *and* "here's an answer". I was self taught in perl, originally from a really lousy book and perldocs. I tell you, that book left me with some moderately bad Perl habits, but also left me at a point where I didn't know something existed so I could look into it further.

Think about all the power of Perl, but not knowing it. Driving a car that you only knew had first gear. My original world of Perl was defined so narrow that for most tasks, I only knew of one way to do things, a bad place to be for Perl.

Even after I started learning more, I wasn't fluent with what modules were on CPAN, and what wheels have already been invented. I'm still not near the point I want to be.

All this is leading to the point of simple questions may open up worlds to people new to Perl. A simple indication to read the docs may not reveal other ways to do things to those struggling, where a code snippet or a reference may.

But you still need to understand, so a enjoiner to look at the docs is still in order. But even better would be a pointer to the appropriate docs - be it in perldocs, a name of a favorite book (or publisher) that covers it, etc. It really encourages people.

=Blue ...you might be eaten by a grue...


In reply to RE: Are there questions to basic? by Blue
in thread Are there questions to basic? by OzzyOsbourne

Title:
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?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others goofing around in the Monastery: (9)
As of 2024-04-18 13:25 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found