[Debburn-devel] [PATCH] cleanup: Use ANSI-style function definitions in cdrecord.c

[Albert Cahalan]

> > 80 columns, if you would, please.
> >
> > I'm actually not insistent upon the 80-column rule - we do all have
> > resizable xterms in this day and age - but it _is_ a good general rule
> > of thumb, to keep lines from becoming unreadably long.
>
> I think 80 columns is worth keeping as a standard. I simply didn't format
> this code to wrap always exactly at 80 columns bebause JS didn't bother
> about it anywhere in his code as far as I could see.

For style, a rule of thumb is better than a standard.

It's nice to keep things somewhat narrow, but please don't
start word-wrapping at more-or-less arbitrary locations just
to satisfy a rule. That belongs in the obfuscated C contest.

(just today I was looking at what appeared to be a
paragraph, but was actually C++ code)

Your editor may support several options for dealing with
the occasional oversize line. Some editors, including both
GUI and text-only, let you scroll sideways so that there
isn't the problem of a fake line ending in your display.
You may need to adjust a config option.