So we have 3 supporters now, Mike,Joep and myself.. Sunish
On Wed, Mar 17, 2010 at 2:42 PM, Joep Suijs <[email protected]> wrote: > Hi Sunisch > > 2010/3/17 Sunish Issac <[email protected]>: > > I think there's only one major difference of opinion in JSG and that's > > having camel case for variables/identifiers. > True, and it was not my option at the time (but 3 spaces indent was ;) > > > > So why not we reconsider the issue ? > Good to reconsider: > > Pro: > - I still think it enhances readability (although you don't need to > exaggerate that. And it is only true if you really use the camel-case > in the same way in all places) > - For me, it would avoid changing from camel case to jallib jsg before > committing ;) > > Cons: > - it will change all API's. I have over 100 projects in JAL and won't > be glad I had to update them all to work with an updated version of > jallib, even now that I am involved and understand why. Most users > don't care and just get confronted with the change... > - it will take a tool to enforce the right casing. Ideal would be to > have a compiler option that makes the compiler case-sensitive and use > that for the continues integration tool. > > Joep > > -- > 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]<jallib%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/jallib?hl=en. > > -- 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.
