My problem with automatic formatting is that it is allways close, but never as good as hand made. This:
// If markup stream is null, that indicates we already
// recursed into
// this block of code and set it to null (below). If we did
// that,
// then we want to go up another level of border nesting.
Is something I see sometimes when using the Eclipse formatter (ctrl + shift + f). So, I wouln't like to format the whole source tree again. I'll take care of the issues you sent this week.
Eelco
Jonathan Locke wrote:
here's a first approximation of K&R braces. i also notice someone has the style of putting spaces inside parens.
frankly, i have no interest in doing any of this by hand and i'd imagine nobody else does either. so one way to fix all this might be to use Eclipse to reformat all the code. i believe it can do this. we just set up a project coding style (which we can even check in and reference in developer docs!) by voting on conventions or whatever and then we can use eclipse to reformat each file with that style template. at least, the beta i looked at several moths ago could do this...
i truly don't care what style we adopt as a team, so long as it's consistent. one good way to take care of this is for someone to make an eclipse code formatting style and send it to the list for evaluation. if there's anything we want to argue about, we can vote to change that style by +1/-1. once we adopt the style, we should stick with it on checkins.
jon
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
