Brian Aker wrote:
> Hi!
>
> 1) Don't use "struct" for a struct. This is C++, isn't needed at all.
++
> 2) Don't use typedef with struct.
++
FWIW- the C++ people seem to follow the convention of declaring classes
as structs if they have no private members. I personally don't like that
and would rather just see class Foo { public: ... } ... but it does seem
to be common practice and saves a line of text for things like:
struct MyCallback
{
int operator(int x, int y) () { return x+y; }
}
thoughts? We should standardize one way or the other, I think.
> 3) I noticed that the codestyle for comments was updated for this
> (unless I am wrong):
>
> /**
> *
> *
> *
> */
>
> The "*" on a blank line. I gotta say... I am not in favor of it. In very
> large part because my editor keeps screwing it up :)
>
> I don't see the need for it... but I can go with majority on it. Though
> if someone has a vim recipe for this... I am game.
I think the continuation *'s are a thing doxygen wants? My emacs knows
how to deal with it, but you're right, my vim seems to not ... I'll go
see if I can find a vim recipe.
OOH. Found it:
" turn on comment continuation for C style comments
set fo+=r " formatoptions r adds new comment line automagically
" only apply on C comments, and mail forwarding "> "
set com=s1:/*,mb:*,ex:*/,:>,fb:-
Works beautifully.
Monty
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
