You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by Richard Feit <ri...@bea.com> on 2004/11/01 16:13:19 UTC

Re: Coding Conventions?

+1 on waiting...
As to the general issue, I've been in favor of "respect the environment" 
in the past, but I could be convinced to go with a standard.  We should 
revisit this after ApacheCon (and once we're solidly past the alpha 
release).

Rich

Ken Tam wrote:

>+1 on not reformatting code prior to ApacheCon.
>
>Given the amount of code already written and its state, I favour a
>"respect the environment" coding convention -- there's de facto
>conventions in various parts of the codebase, and devs should follow the
>conventions of the area they're contributing in.
>
>  
>
>>-----Original Message-----
>>From: Michael Merz [mailto:michael.merz@gmail.com] 
>>Sent: Sunday, October 31, 2004 11:22 AM
>>To: beehive-dev@incubator.apache.org
>>Cc: davanum@gmail.com; dolander@gmail.com
>>Subject: Re: Coding Conventions?
>>
>>+1
>>
>>I agree with Daryl, we've used the same philosophy for WSM so far.
>>Since the adoption of coding conventions at this point would 
>>complicate history diffs (and therefore merges, too), I, too, 
>>would like to suggest to postpone this until after ApacheCon. 
>>Let's talk about this after (or during) ApacheCon. Sound good?
>>
>>Cheers,
>>
>>-michael
>>
>>Date: Sun, 31 Oct 2004 07:21:04 -0700
>>From: Daryl Olander <do...@gmail.com>
>>Subject: Coding Conventions?
>>Content-Type: text/plain; charset=US-ASCII
>>
>>
>>NetUI hasn't decided that it wants a coding convention. We've 
>>never had one.  One person's "looks nice" is another persons "sucks".
>>
>>I suggest we don't do this until after Apachecon because if 
>>we do it now it will significantly increase the difficulty of 
>>merging changes from one branch to the other.
>>
>>
>>On Sun, 31 Oct 2004 06:45:42 -0500, Davanum Srinivas 
>><da...@gmail.com> wrote:
>>    
>>
>>>Michael,
>>>
>>>Since diff's are going to be problematic AND we want the 
>>>      
>>>
>>code to look 
>>    
>>
>>>nice and consistent for ApacheCon....Shall i do it ASAP? If 
>>>      
>>>
>>we do this 
>>    
>>
>>>once early in the project it's easier in the future (when 
>>>      
>>>
>>folks really 
>>    
>>
>>>need to look at diff's carefully)
>>>
>>>-- dims
>>>
>>>On Sat, 30 Oct 2004 23:01:07 -0700, Michael Merz 
>>>      
>>>
>><mi...@gmail.com> wrote:
>>    
>>
>>>>Hi Dims,
>>>>
>>>>Thanks much for all the Axis-specific and non-Axis-specifc work 
>>>>you've put into the WSM project! It's much appreciated! :)
>>>>
>>>>So far, we've not adopted Sun's coding conventions (I 
>>>>        
>>>>
>>assume you're 
>>    
>>
>>>>referring to 
>>>>        
>>>>
>>http://java.sun.com/docs/codeconv/CodeConventions.pdf).
>>    
>>
>>>>While I would generally not have a problem with reformatting the 
>>>>code, I would suggest to do this consistently for the entire 
>>>>Beehive-project (if controls and netUI haven't already 
>>>>        
>>>>
>>done so). I 
>>    
>>
>>>>would anticipate the major downside to be potential problems with 
>>>>diff'ing the history of files.
>>>>
>>>>Cheers,
>>>>
>>>>-michael
>>>>
>>>>Date: Fri, 29 Oct 2004 11:20:54 -0400
>>>>From: Davanum Srinivas <da...@gmail.com>
>>>>Subject: Coding Conventions?
>>>>Content-Type: text/plain; charset=US-ASCII
>>>>        
>>>>
>>>      
>>>
>>>>
>>>>
>>>>Are there any specific coding conventions to follow? would folks 
>>>>mind if i reformat (specifically the WSM module) to SUN coding 
>>>>specifications?
>>>>
>>>>thanks,
>>>>dims
>>>>
>>>>--
>>>>Davanum Srinivas - http://webservices.apache.org/~dims/
>>>>
>>>>        
>>>>
>>>--
>>>Davanum Srinivas - http://webservices.apache.org/~dims/
>>>
>>>      
>>>
>
>  
>