Svn book and sample Perl code style

I've gotten some feedback on my cleanup of the sample Perl script
in ch05.xml (svn-ch-5-sect-3.4-ex-1) of the Subversion book that
was basically, "don't use the Subversion coding style, use the
style that most Perl code uses".

I don't recall any discussion and policy on the coding style that
should appear in the book for non-C languages. I've been using the
Subversion coding style for all the Perl code that I check into the
svn tree, hence using that for the book. Should we use the default
code style for Perl instead?

Another question. Writing that script to check for errors and
doing all the things that a good script should do will take more
space in the book, but makes me feel better as it reflects the
quality that we put into the Subversion code. Where do people
stand on this (length vs quality)? Somebody may type that script
into their system and use it themselves, so I'm thinking it should
be good code.

Best,
Blair

-- 
Blair Zajac <blair@orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org