Re: Coding standards

[Phil Edwards <pedwards at jaj dot com>]

>  > Some of us do it all the time, because there's a lot of editors which can
>  > handle looking for ^foo regexps but don't use any kind of tags file.
>
> Surely searching for declarations with ^foo is a pointless excercise
> when namespaces and/or nested class declarations are thrown into the
> mix?  IMHO this goes to show that using C coding standards for C++ just
> doesn't work.

It's only useful for definitions, yes, but not only for free functions.
Nobody says that the :: can't come at the end of a line and the function
name start the next one.

Again, I'm not recommending it for libstdc++.  I'm saying that the
practice /is/ used, when tags files and point'n'click source browsers
are not in the mix.  That's all.


(If you reply to the list, please don't cc another copy to me.  Thanks!)
Phil