This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [wwwdocs] Update coding conventions for C++


On 6/27/12, Gabriel Dos Reis <gdr@cs.tamu.edu> wrote:
>
> [...]
>
> | > Two spaces for members is common practice with GNU, and it seems to be
> | > used for libstdc++.
> | >
> | > One space for protection labels is not something I have heard of before
> | > and libstdc++ uses no indentation for them.
> | >
> | > A freshly started emacs also doesn't indent access labels.
> | >
> | > I do think there is some value in using the same coding style for
> | > libstdc++ and the compiler.
> |
> | I agree here.  It's the same we do for case labels.
> |
> | Richard.
>
> I think we reached total agreement :-)

I have changed the convention to not indent the protection label.

-- 
Lawrence Crowl


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]