Call me old-fashioned, but I almost never use the following (although sometimes I use modules that do).
- source filters
- prototypes
- formats (well, that would be old-fashioned)
- tie (although it has been a helful hack for debugging in some occasions)
- attributes (including lvalue)
- barewords (not counting those that are allowed under "use strict")
- "experimental" regex features. They look cool, but I've been bitten by their bugs too many times. I was surprised to see that Damian recomends some of them as best practices!
- AUTOLOAD
- CHECK, INIT
- CORE::GLOBAL (sometimes useful, such as for testing)
- Most of the variables on perlvar, but that's too long to mention here. Many of the functions in perlfunc as well.
- <> to glob
- foreach (heh, I'm to lazy to type those extra characters. But of course I use for!)
- pseudohashes (they have been deprecated anyway)
- version strings (also deprecated)
- until
-
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.
|