Code Width and Comment Style (Was: What counts as a fork?)

[Paige DePol <lual@...>]

Alexis <flexibeast@gmail.com> wrote:

> 
> Paige DePol <lual@serfnet.org> writes:
> 
>> From a code refactoring point of view, is there still a need to limit
>> code to 80 columns?
> 
> Not sure about the code-refactoring POV, but even if technology allows
> for more columns, limiting code to less than 80 columns might benefit
> comprehensibility and speed of reading:
> 
> "In order for on-screen text to have both the best speed and
> comprehension possible about 55 cpl should be used."
> 
> -- https://en.wikipedia.org/wiki/Line_length

Yes, for typography, as in books and the like, that does make sense,
however, source code isn't quite the same as written text in terms
of reading and parsing. Though, Lua is probably closer than C! ;)

In Objective-C, for example, the selectors can be quite verbose and
statements can exceed 80 columns fairly quickly, especially when
doing logic statements. Though, that said, I have seen where people
break down the selector by sections onto multiple lines as well.

One thing I was contemplating, and have seen in other projects, was
to align the comments on the 81st column, with a total page width
of 132 columns. So 80 columns for code, and 52 columns for comments.

What standards for code width and comments styles do you all use?
Not for Lua, mind you, but for C or C-like languages. Of course,
this will also depend on whether tabs or spaces are used... I do
not want to get into a debate about spaces vs tabs, I am just
curious about code width and comment styles is all! 

~Paige