Hi there I agree with most of the points you brought up. I've wondered myself in the last few days if I should dare to make another attempt to bring this up. The XML project refers to the Sun Coding Conventions for Java style. But as you will all agree this is not enough. It leaves too much room for intepretation. I like to propose the following: As Jörg suggests I'd like to have a code style document nailed down and published. The Sun Coding Conventions should be the base and we add some restrictions based on this discussion (4 spaces instead of tabs, naming conventions on variables etc.). This is the "MUST" part of it. Then, I think some of Jörg's points are suggestions/pointers that make the code more readable. And this would be the "SHOULD" part of it.
What do you think? I'll volunteer to write the style doc and go over the whole codebase after my two-week absence starting Sunday. An additional possibility is to use checkstyle to help analyze and maintain the quality of the code. The Avalon subproject does that. I'll check what it can do for us. As an aside: I'm currently somewhat hesitant to do changes in the docs. When can we expect the refactored docs? Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
