Hard column wrap

Matthew Newton mcn4 at leicester.ac.uk
Tue Mar 19 15:51:34 CET 2013

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

...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.

> > 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.

>   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.

...and why unlang isn't a programming language, as you can't do 

  } else {


> > if (braceless)
> > 	alan_will_beat_you_with_sticks;
> > else if ((assignment = nested)
> > 	with clubs;
>   Hmm.... clubs.

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


Matthew Newton, Ph.D. <mcn4 at le.ac.uk>

Systems Specialist, Infrastructure Services,
I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom

For IT help contact helpdesk extn. 2253, <ithelp at le.ac.uk>

More information about the Freeradius-Devel mailing list