Blair Zajac wrote:
>
> 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?
(Opinion of a lurker)
There is no such thing as a default Perl code style, and I think I've
seen enough perl code to state this confidently.
Stick with perlstyle(1)'s advice and "be consistent" -- with Subversion's
code style. Your idiom is perlish enough. (That would be different
if your perl contructs looked like roughly translated C.)
> 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.
I agree.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 2 18:30:19 2003