For ACE, we have an Eclipse formatter file; could we update this and attach it 
to the page?

Angelo

On Oct 11, 2010, at 11:33 AM, Ivo Ladage-van Doorn wrote:

> Although it is indeed not (yet) documented on the WIKI, the conventions used 
> until now are the ones used internally by GX. Not by coincidence they match 
> almost perfectly (from what I can see after scanning it for a few seconds) 
> with the conventions Marcel proposed. Only differences I see for now are the 
> new lines in try/catch and if/else. Personally I prefer the conventions as in 
> the Apache ace conventions.
> So my suggestion: 
> http://incubator.apache.org/ace/java-coding-style-guide.html rulez!
> But also agree with Bram; should add line length 120. Line length 80 is just 
> not of this time anymore?
>  
> Regards, Ivo
>  
>  
> From: amdatu-developers-bounces at amdatu.org 
> [mailto:amdatu-developers-bounces at amdatu.org] On Behalf Of Marcel Offermans
> Sent: maandag 11 oktober 2010 10:59
> To: amdatu-developers at amdatu.org
> Subject: Re: [Amdatu-developers] code style / formatting?
>  
> On 11 Oct 2010, at 10:53 , Bram de Kruijff wrote:
> 
> 
> I noticed that there is no code style or formatting documented on the wiki. 
> (This was after I ran into conflicts :s) It seems there are some conventions 
> being used be not very consistently. Not trying to get into a religious 
> discussion about code style / formatting conventions here, but I would very 
> much appreciate some basic rules as they will make diffing, patching en IDE 
> configuration a lot easier.
>  
> What about starting with:
>  
> http://incubator.apache.org/ace/java-coding-style-guide.html
>  
> Greetings, Marcel
>  
> _______________________________________________
> Amdatu-developers mailing list
> Amdatu-developers at amdatu.org
> http://lists.amdatu.org/mailman/listinfo/amdatu-developers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://lists.amdatu.org/pipermail/amdatu-developers/attachments/20101011/c92171c8/attachment.html
 

Reply via email to