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

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

This is great; I really appreciate the discussion and the links.

Are there other, similar shortcuts, conveniences, or whatever you wish to call them, that one needs to be aware of or careful in using? (In re-reading the original post, I realize that I wasn't completely clear in the main reason for the message.)

One reason I am asking is this: a book I am re-reading discussed the diamond as a shortcut (which, thanks to merlyn, I understand that it's not). That didn't sit right. So, I asked.

Are there other, common misconceptions taught as "the proper way?" (What got me thinking along these lines is an online DBI tutorial from a web development site that a) did not use, b) did not taint, c) did not validate data. After lurking around the last several weeks, I realize how dangerous that is. So, I got to wondering what other "bad habits" I've picked up.)

In reply to RE: Regarding style by footpad
in thread Regarding style by footpad

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.