For user-defined functions, I always use parens.
This is being kind to the Perl parser, making it easier
and less error-prone to switch between "use" (compile-time)
and "require" (run-time).
I've seen Perl newbies spend hours trying to figure out
what is wrong because they didn't use parens when calling
their user-defined functions. For example:
use strict;
Fred;
sub Fred { print "in function Fred\n" }
produces the error Bareword "Fred" not allowed while "strict subs" in use at fn.pl line 2..
Re style guide, I quite like Abigail's My coding guidelines.
If you know of any other good ones, please let
me know, because I hope to (eventually) write a tutorial
that will include recommendations on Perl style.
Update: See also: Re: New Discovery!!! (sub call without parentheses) - Coding Style
-
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.
|