"Malte S. Stretz" <[EMAIL PROTECTED]> writes: > I think the last discussion about a coding style dies off before we came to > a real conclusion.
I came closer. The style I documented is getting there, but it still needs some more tweaking to match current practice closer. I think we should stick reasonably close to our current practice, but I am amenable to changing a few minor things. > While I was browsing the Apache site a few minutes ago, I noticed that > there's something called "Apache Developers' C Language Style Guide" [1]. > It looks sane (mostly like the stuff we were discussion) and like something > we could use for Perl, too. I am in 100% agreement that we could use something like that. It's even better than perltidy options, perhaps. :-) Since I did the last pass on the perltidy options, feel free to take the next pass. > That way we won't have to argument about tabs or not and two or four spaces, > just follow the style used within the group we're now a part of. I would > even use four spaces as suggested by the guide, just to come to an > conclusion ;-) That's not one of the things I'm not currently in favor of changing. 2 columns of indentation is my current preference. I might be willing to consider 4, but that much reindentation would absolutely destroy line annotations in the SVN tree. Daniel -- Daniel Quinlan anti-spam (SpamAssassin), Linux, http://www.pathname.com/~quinlan/ and open source consulting
