This one time, at band camp, Brian Behlendorf said:
BB>On Fri, 15 Aug 2003, Robert Stupp wrote:
BB>> Code formatting could be performed through a "plugin" on the server side
BB>> of CVS, which formats the Java code on each commit. So nobody would have
BB>> to take care of code formatting.
BB>
BB>N
On Fri, 15 Aug 2003, Robert Stupp wrote:
> Code formatting could be performed through a "plugin" on the server side
> of CVS, which formats the Java code on each commit. So nobody would have
> to take care of code formatting.
No. Server-side munging of content is error-prone and bad form.
You
Siva wrote:
Sun says
"Avoid lines longer than 80 characters, since they're not handled well by
many terminals and tools. "
IMO,having everything in the field of vision is better than to scroll and
see.
While it is generally a good idea if you plan on printing out your code, I
find code forced into
t;
To: <[EMAIL PROTECTED]>
Sent: Friday, August 15, 2003 7:28 PM
Subject: RE: coding conventions
> I doubt that the 80 cols limit will be a coding convention.
>
> Personally I keep Eclipse with the print margin on at 80, just to keep the
code
> readable on screen and, if needed,
more of a good practice than a strict convention.
Daniel farinha
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Fabrice M.
Sent: 15 August 2003 13:42
To: [EMAIL PROTECTED]
Subject: Re: coding conventions
Aditya Gore <[EMAIL PROTECTED]> writ
Aditya Gore <[EMAIL PROTECTED]> writes:
> I am something of a newbie to open source...
> Was browsing through the code and came across many files
> that have lines that extend way beyond 80 characters. Cutting
> these into multiple lines could be a task in itself. Do such
> things qualify for a pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Code formatting could be performed through a "plugin" on the server side
of CVS, which formats the Java code on each commit. So nobody would have
to take care of code formatting.
BTW: The code formatter (ctrl-shift-F) in Eclipse is fine and configurable
