Re: [JPP-Devel] Style Sheet For Java FOSS Coding

2008-07-02 Thread Sunburned Surveyor
I wasn't actually referring to the core. I was hoping to include my code in the plug-in programmer's guide that I am working on. Still, every drop adds to the bucket. :] Landon On Wed, Jul 2, 2008 at 11:59 AM, Larry Becker <[EMAIL PROTECTED]> wrote: >>If you change only the little piece of code

Re: [JPP-Devel] Style Sheet For Java FOSS Coding

2008-07-02 Thread Larry Becker
>If you change only the little piece of code you have to patch, >without touching or reformatting the whole code, how does it matter how you format >that little piece??? Paolo hit the nail on the head with this comment. No matter what you decide to use as coding standards, there has been a preced

Re: [JPP-Devel] Style Sheet For Java FOSS Coding

2008-07-02 Thread Paul Austin
I think that using an if/.else statement is much more readable than the ?: operator. It's just another one of those coding religious wars such as if the { should be on the same or the next line. Paul - Sponsored by: Source

Re: [JPP-Devel] Style Sheet For Java FOSS Coding

2008-07-02 Thread edgar . soldin
Hi Paul, > >1. Avoid using inline conditionals x ? y : z > whats wrong with inline conditional statements? .. regards ede > Paul > > Sunburned Surveyor wrote: >> I'm thinking about the preparation of a short document with code style >> tips for Java FOSS programming. >> >> There is the concis

Re: [JPP-Devel] Style Sheet For Java FOSS Coding

2008-07-02 Thread Paul Austin
Landon, Here are my comments 1. Code formatting is very important in the FOSS world as you have many developers modifying the code. If you have consistent formatting then when you do a diff/merge you can see the real changes between the code and not just the differences in