Peter Courcoux <[EMAIL PROTECTED]> writes:
>Henning,
>Some of that is my fault. I don't have the Turbine coding preferences in
>my copy of eclipse where I am working at the moment and Eric has
>committed some patches I prepared. It should be corrected... and I'll
>set up the correct preferences!
Actually I don't care much about the indent style, but as there are
many people working on the code, I'd like to avoid the "I touched the
file, let's reformat it" checkins, which clutter up actual code
changes in the CVS.
A really _cool_ thing would be a SCM viewer which can skip indent
changes when diffing versions.
Regards
Henning
>Peter
>On Wed, 2004-05-26 at 16:57, Henning P. Schmiedehausen wrote:
>> [EMAIL PROTECTED] writes:
>>
>> Hi Eric,
>>
>> something I noted in your last few checkins is, that the "Turbine
>> Style Guide" for Code indentiation seems to have changed in the last
>> few months. I also noted that the "coding style" page has gone from
>> the Turbine 2.4 web site (or I was not able to find it).
>>
>> Is this intentional? While I must admit (though I will always be a
>> BSDian when it comes to indent), that
>>
>> try {
>> something;
>> } catch (Exception e) {
>> do something else;
>> } finally {
>> do another thing;
>> }
>>
>> has its merits, I always considered this not very readable for method
>> definitions:
>>
>> > + public List getKeys() {
>> [...]
>> > + }
>>
>> This is not intended as critisism, I was just wondering. In the end,
>> every indent style is just "getting used to it" and getting support
>> from emacs to auto-indent it. :-)
>>
>> Regards
>> Henning
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
"Fighting for one's political stand is an honourable action, but re-
fusing to acknowledge that there might be weaknesses in one's
position - in order to identify them so that they can be remedied -
is a large enough problem with the Open Source movement that it
deserves to be on this list of the top five problems."
-- Michelle Levesque, "Fundamental Issues with
Open Source Software Development"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
