At 08:24 AM 11/3/2001 +0000, Greg McCarroll wrote: >* Stephen Adkins ([EMAIL PROTECTED]) wrote: .... >I'm just going to play devils advocate here and I apologise for coming >in a little late in this thread, however ... > >Lets just assume that someone writes a nice module for CPAN/P5EE, that >is in their own style. Are we really going to ask them to change the >style? I don't really think there will be that many benefits in this >case as historically modules have been written and maintained by just >one person. I'd also suggest that the main `applications' of P5EE >(messaging daemons etc.) will follow suit.
My opinions on this... * a style guide makes code uniformity *possible* * the culture of the P5EE community (as it evolves) and the realities of the P5EE code base (as it evolves) will determine the degree to which it is *practical* * we each have good sense and can pretty much tell which parts of the guide are advice and which are more important for the functioning of the community (after all, we have all lived successfully in the presence of a general Perl style guide, "perlstyle") * I think we pretty much all agree there will be no style-guide police ;-) >The idea of a mass of people all working together on a huge CVS tree >is imho, at best over optimistic. I have no idea how this will evolve. I'm just taking one step at a time at what seems reasonable to me, and others will do the same. If we have any code at the "center" which is accepted by the community at large, a style guide accepted by the community is a sensible start. Stephen P.S. I deleted the "shift" section altogether from the style guide.
