Brent Clark wrote:
Hi all
Hi there
I seem to be having a few run ins with the "Project Leader", in terms of
my coding style.
Im very much for modularizing my work - hence the OO concept. That is
creating packages using return in my subroutine etc (Oh and using strict)
But the ex Cobol Project Leader does not want .pm. Varibables has to be
of a certain naming type convention like the value from a html text box
has to begin
with an i (e.g, $iabc), and strict does not need to be used, hell
neither is #!/usr/bin/perl -T.
Consistency is important. If there are 5000 source files, 50 of which
you wrote 100% and another 350 you wrote between 1% and 5% of, then your
coding style is in the minority.
Obviously prepending a simple 'use strict;' to every file isn't that big
of a deal (though it may upset people to see that someone massively
modified all of the files without an explanation), but it's probably not
worth it - if you don't use strict, what is the likelihood that your
code will be strict?
Basically, you can't have everything your way unless you are in control.
If you're the one in charge, your style goes. Otherwise, either do
things the most consistent way, or get out (and do things your way).
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
