Re: [PATCH] [v8] safecrlf: Add mechanism to warn about irreversible crlf conversions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Mon, 4 Feb 2008, Steffen Prohaska wrote:

> On Feb 4, 2008, at 4:02 PM, Johannes Schindelin wrote:
> 
> > On Mon, 4 Feb 2008, Steffen Prohaska wrote:
> > 
> > >  - refactored to lines max 84 chars long.
> > 
> > Why 84?  I think the standard is still 80.
> 
> Because the surrounding code already had lines with more than 80 
> characters and the most natural refactoring without too much wrapping 
> effort resulted in 84.
> 
> Is 80 a strict limit?

It is not a _strict_ limit.  But it is a limit [*1*].  84 is not.

Ciao,
Dscho

*1*: Linux' CodingStyle says/said this:

Statements longer than 80 columns will be broken into sensible chunks. 
Descendants are always substantially shorter than the parent and are 
placed substantially to the right. The same applies to function headers 
with a long argument list. Long strings are as well broken into shorter 
strings. The only exception to this is where exceeding 80 columns 
significantly increases readability and does not hide information.

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux