Stephen Adkins [EMAIL PROTECTED] writes:
Hi,
I have grabbed the Slash style guide, removed/modified
the offending sections (exit/die, DESTROY, shift), and
created a proposed P5EE style guide.
All comments are welcome. This is to make code consistency
possible, not to make our lives
Hi,
The Slash style guide declared that Perl 5.005_03 and 5.6.0
were supported:
We code everything to perl 5.005_03. Some day we may switch to
take advantage of perl 5.6 features. Regardless, all code
should run on perl 5.005_03 or any later version of perl 5.
All of the core P5EE
Stephen Adkins [EMAIL PROTECTED] writes:
Hi,
The Slash style guide declared that Perl 5.005_03 and 5.6.0
were supported:
We code everything to perl 5.005_03. Some day we may switch to
take advantage of perl 5.6 features. Regardless, all code
should run on perl 5.005_03 or any
While considering coding style, what do you think about running code
through something like perltidy? (http://perltidy.sourceforge.net/)
It might help to enforce some of the style standards set here, while not
making it too much of a hassle for those who are more used to other
styles or
On Fri, 2 Nov 2001, Dave Rolsky wrote:
This is Perl, not Java (thank dog), so let's keep it
that way.
ok mr exception hierarchy :)
