Hard column wrap

Arran Cudbard-Bell a.cudbardb at freeradius.org
Tue Mar 19 16:01:11 CET 2013

On 19 Mar 2013, at 10:51, Matthew Newton <mcn4 at leicester.ac.uk> wrote:

> On Tue, Mar 19, 2013 at 10:01:09AM -0400, Alan DeKok wrote:
>> Arran Cudbard-Bell wrote:
>>> For years the official maximum line length in the FreeRADIUS
>>> has been 80 columns. There was no real reason for this other
>>> than to satisfy our project leader's nostalga for VT100
>>> displays.
>>  Well... not *just* VT100.
> This is nearly moving forward to a VT220 with a 132 column
> display...
> ...which is so hard to read you just set it back to 80 as soon as
> possible. (Yeah, they're still useful for managing switches.)
> I always try and code to 80 chars wide. Looking at code in a
> default xterm is really annoying when it goes over 80 chars, and
> it's hard to follow the code to the next line. But it's your
> decision. My xterm will stretch.

It was getting annoying. 
There are some situations where you can't avoid the levels of nesting,
"and doing hard "
" truncation of log "
"messages is an "
"absolute PITA."

>>> switch (es)
>>> {
>>  No... the brace goes on the same line as the switch statement.
> Yuck - agreed. Function declarations on the next line, everything
> else at the end of the same.


switch (foo) {
case bar:


looks squished to me. But whatever.

>>  Half of my screen is taken up by brackets.  If you can't figure out
>> what code belongs where from the indentation alone, you shouldn't be
>> programming.

> There's a spare bracket in that statement that could be used to
> store the clubs, if required.

It was omitted for just that reason.

More information about the Freeradius-Devel mailing list