Sorry I need to be more clear on this..
the problem for me is that kawa seems very happy with the "
method
{
}
indentation and makes it automated.
most tools just follow the SUN coding standard of
method {
}
and naturally indent in that way and get very confused by the first one.
Frankly it's anoying either way (there is some clarity to the first, a SUN
standard and tools behind the second )
as with all important problem I propose a toss up :)
heads we go A tails we go B...
:)))
how do we do a that on our mailing lists??????
ah man simple things in life really are complicated sometimes:)
any other way? to make a draw? i will be glad to twist anyJ non-standard
conf either way.
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
|Sent: Monday, December 11, 2000 8:21 PM
|To: jBoss Developer
|Subject: RE: [jBoss-Dev] More: Proxy & handle changes
|
|
|guys the SUN standard is very clear :)
|
|marc
|
|
||-----Original Message-----
||From: [EMAIL PROTECTED]
||[mailto:[EMAIL PROTECTED]]On Behalf Of Rickard Oberg
||Sent: Monday, December 11, 2000 1:02 PM
||To: jBoss Developer
||Subject: Re: [jBoss-Dev] More: Proxy & handle changes
||
||
||> This brings up a topic I've been intending to ask the list about. Are
||> there coding standards for JBoss?
||
||Not formal, no. You're encouraged to use the style employed in the bulk of
||the code, i.e. "Rickard style".
||
||> I've been using the templates in
||> src/etc (which are out of date, BTW, re: [jJ]Boss and [L]GPL) along with
||> what appears to be the predominant indenting style (which I think of as
||> "Rickard style"), which seems to be:
||> - indents are 3 spaces
||> - braces go on a new line at the same indent level as the previous line
||> - otherwise standard Java style as from Sun.
||
||Correct.
||
||I try to let people use their preferred indenting/bracing standard
||(discussions on this topic tends to get religious and don't ever end), but
||to me anything other than the above mentioned is unreadable so if
|I need to
||read code to get something done, and it doesn't follow the above I usually
||"fix it up" in the process.
||
||> I'm not hugely fussed about the exact number of spaces an indent is, but
||> I am fussed about making things consistent, at the very least within
||> each file. I also *despise* tab characters - there is a lot of code in
||> JBoss that just can't be read without adjusting the size of a tab
||> character to something other than 8 - this is simply nonsense.</foam>
||
||Agree. I think I used tab chars in the beginning but now I only
|use spaces.
||
||/Rickard
||
||ps. And yes, I agree with your conclusions re: explicit package imports.
||
||
||
||
||
|
|
|
