At 01:59 PM 11/1/2002 -0500, Stephen Adkins wrote:
The style guide you were looking for is here.
http://www.officevision.com/pub/p5ee/software/htdocs/P5EEx/Blue/perlstyle.h
tml
The references are out of date.
It should read:
=head1 ACKNOWLEDGEMENTS
This style guide was based
Hello all,
I read the P5EE style guide a while ago, and one thing that strikes me
as odd is in the 'Warnings and Strict' section:
It says that code should run cleanly with 'use strict' and '-w'
(warnings) enabled. It then goes on to say that 'The one exception is
the ``Use of uninitialized
[EMAIL PROTECTED] wrote:
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
Greg McCarroll [EMAIL PROTECTED] writes:
* Stephen Adkins ([EMAIL PROTECTED]) wrote:
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
On Sat, 3 Nov 2001, brian moseley wrote:
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 :)
Hey, just cause Perl isn't Java doesn't mean we can't borrow the _good_
ideas from Java ;)
-dave
quicker.
I'd definitely suggest that we add to the style guide that all publicly
available APIs should do argument validation. I don't know if this is a
style thing so much as a code quality thing.
Anyway, regardless of what validation implementation we come up with I'm
all for having one
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
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 :)
