Hi Mike, On Mar 17, 8:16 am, "m...@watty" <[email protected]> wrote: > > Don't change any existing code. New code can still be to existing > style guide. Just allow new code to use camelcase also where it's > appropriate (in the eye of the beholder).
May I ask-- are you interested in working towards an revised style guide, and then be willing to adhere to it, even if it doesn't match 100% with your current/personal style? As an example, I don't care for the 3 spaces either, but I can live with it, especially since jallib.py has a nice re-indent option for when I forget. My standard practice is: jallib.py reindent and jallib.py validate before I add or update things to SVN. William -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
