Perl Best Practices Page

: Always include use strict; and use warnings; to catch common syntax errors and unsafe practices early.

: Throw exceptions using croak or die instead of returning special "failure" values like undef . Perl Best Practices

: Use Perl::Tidy to automatically format code, ensuring all team members use the same indentation and bracket styles. : Always include use strict; and use warnings;

Consistency is more important than any single style choice. Automated tools help enforce these standards: : Always include use strict