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] |
On 09/25/2013 09:48 AM, Paolo Carlini wrote:
Yea. I actually reviewed the libstdc++ guidelines to see where they differed from GNU's C guidelines.On 9/25/13 10:46 AM, Andrew MacLeod wrote:I was going to bring it up at some point too. My preference is strongly to simply eliminate the space on methods...Which wouldn't be so weird: in the libstdc++-v3 code we do it all the time.
I'm strongly in favor of dropping the horizontal whitespace between the method name and its open paren when the result is then dereferenced. ie
foo.last()->e rather than foo.last ()->e.However, do we want an exception when the result isn't immediately dereferenced? ie, foo.last () or foo.last()?
jeff
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |