The backend Perl code must conform to the following style guidelines. If you find any code which doesn't conform, please fix it. These requirements are intended to maintain consistent, organized, professional code.
Proper indentation is very important. Just because the code lines up properly in your editor of choice, does not mean it will line up properly for someone else working on the project. This can be very annoying. These requirements will prevent this.
Tabs should be used to indent all code blocks. Spaces should never be used to indent code blocks. Mixing tabs and spaces results in misaligned code blocks for other developers who prefer different indentation settings. Consider the following code block which is indented with all tabs (shown with and without whitespaces):
|
|
|
Indented properly with tabs. | Code is lined up properlproperly. | Indentation width set changed to 8. |
...
A mix of tabs and spaces is only acceptable preferred in order to indent sections of code which spans span multiple lines but is not an entire block between curly braces. The following example illustrates this:
...
|
|
The editor's indentation with is changed to 8. | The code remains lined up properly and easy to read. |
Comment as much as sanely possible
...
!
There should always be at least 1 space between the # character and the beginning of the comment. This makes it a little easier to read multi-line comments:
No |
---|
...
Yes |
---|
...
#Comments are your friend, they help |
...
#other developers understand your brilliance. |
...
# |
...
Comments are your friend, they help |
...
other developers understand your brilliance. |
...
No |
---|
...
Yes | OK | OK | |
---|---|---|---|
my $m = '00:50:56:12:88:99'; |
...
my $mac_address = '00:50:56:12:88:99'; |
...
for (my $loop = 0; $loop<=10; $loop++) { |
...
for (my $i = 0; $i<=10; $i++) { |
No |
---|
...
Yes | No | Yes | |
---|---|---|---|
my $ip_addr; | my $ip_address; | sub get_comp_name { |
...
sub get_computer_name { |
...
...
No |
---|
...
Yes | No | Yes | |
---|---|---|---|
sub getcomputername { | sub get_computer_name { |
...
my |
...
$endtime; |
...
my |
...
$end_time; |
No | Yes |
---|
...
sub updateRequestState { | sub update_ |
...
request_ |
...
state { |
...
No | Yes |
---|---|
my $requestState; | my $request_ |
...
state; |
Yes |
---|
...
our $SOURCE_CONFIGURATION_DIRECTORY = "$TOOLS/Windows"; |
No |
---|
...
Yes | |
---|---|
my $ipAddress; |
...
my $ip_ |
...
address; |
All modules and subroutines must contain a POD documentation block describing what it does. POD is "Plain Old Documentation". For more information, see:
...
Code Block |
---|
#///////////////////////////////////////////////////////////////////////////// =head2 my_subroutine_name Parameters : none Returns : boolean Description : This is what the subroutine does. These lines must be 80 characters or less. Additional lines must be indented with spaces, not tabs. =cut sub my_subroutine_name { } |
There are several utilities available for generating formatted POD documentation including pod2text and pod2html. It is a good idea to run a module through one of these utilities before committing updates.
There should be a space between every control/loop keyword and the opening parenthesis:
No | Yes | No | Yes |
---|---|---|---|
if($loop_count <= 10) { | if |
...
($loop_count <= 10) { | while($loop_count <= 10) { | while ($loop_count <= 10) { |
There should be a space between every closing parenthesis and the opening curly bracket:
No | Yes | No | Yes |
---|---|---|---|
if ($loop_count <= 10){ | if ($loop_count <= 10) { | while ($loop_count <= 10){ | while ($loop_count <= 10) { |
...
'else' & 'elsif' statements should be on a separate line after the previous closing curly brace:
No | Yes |
---|---|
if ($end_time < $now) { | if ($end_time < $now) { |