This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Thoughts on doxygen for internal documentation
- From: law at redhat dot com
- To: Theodore Papadopoulo <Theodore dot Papadopoulo at sophia dot inria dot fr>
- Cc: Diego Novillo <dnovillo at redhat dot com>, gcc at gcc dot gnu dot org
- Date: Thu, 16 Jan 2003 11:17:03 -0700
- Subject: Re: Thoughts on doxygen for internal documentation
- Reply-to: law at redhat dot com
In message <200301161803.h0GI3DYV018983@mururoa.inria.fr>, Theodore Papadopoulo
writes:
>
>
>law@redhat.com said:
>> I'll note that /** is contrary to the GNU coding standards.
>
>Not really answering in this thread, but this kind of comment make me
>often wonder whether these coding conventions are sometimes reviewed
>and updated. The world is changing around us, the rules should change
>accordingly....
>
>As an example, I always wondered why the rule of 80 columns is still
>that strict. IMHO often code can be more readable using longer lines
>(still with a reasonnable limit, just an higher one). Yes I know, some
>people still have a very old 80 columns VT100, but those cannot be
>that many ? Indeed, mail reader sometimes have this 80 limit constraints,
>but then problems with line wrapping by mailers happen also with 80
>columns... So why keeping this constraints and not updating it to
>something more sensible such as eg 132 colums.
I've known GCC hackers (who shall remain nameless) who didn't use
graphical displays. Instead they used 24x80 screens and linux's
virtual terminals. Hell, I still do it myself when traveling.
jeff