Quoting "Jostein Chr. Andersen" <jostein@josander.net>:
> On Sunday 30 November 2003 23.31, Branko ÄŒibej wrote:
>
> > >Log:
> > >* doc/book/book/ch05.xml (svn-ch-5-sect-3.4-ex-1):
> > > Do a decent attempt at making the sample Perl script for making
> > > incremental backups good quality Perl, use Subversion bracket
> > > coding standard,
> >
> > Ouch. If we write Perl examples, I suggest using Perl's recommended
> > conding standards. I think this is the first Perl script I've seen
> > that uses the GNU brace indentation convention.
>
> Then you should look here:
> packages/win32-innosetup/tools/*.pl :-)
>
> Blair are declaring variables, are using "use strict", using a strict
> syntax and have a clean style. This is good!
>
> It's probably no such thing as "Perl's recommended coding standards" but
>
> many Perl programmers like the old Kernighan & Ritchie style:
>
> if ($foo = 0) {
> do something unredable;
> } elsif ($foo = 1) {
> do something nastier;
> } else {
> make gstein and others port it to python;
> }
This, plus using perl -w and strict, is IIRC exactly the recommended Perl
coding standard described in the Perl man pages.
> The crap above combined with the lack of not declaring variables and
> other funny stuff have made many Perl scripts very hard to maintain and
> understand.
Badly written programs are hard to understand. That has nothing to do with Perl.
My point is that it makes as much sense to adher to the Perl recommended style
as to the Java recommended style.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 1 18:24:46 2003