Le Vendredi 15 Décembre 2006 09:44, Niklas Nebel a écrit : > Thorsten Behrens wrote: > >> A little bit of naming convention is certainly needed. Nobody wants to > >> see a mixture of > >> Foo aFoo(maFoo); > >> CFoo foo(_foo); > >> foo f_(f); > >> even if it's in different modules. > > At least it was my impression up to now that the whole thing is supposed > to be "how we do things at OOo", not another list of "C++ best > practices".
I agree with Niklas. It is important for external contributors who may start to write patches by their own before contacting the OOo team to integrate them in trunk. For them, it would be nice to have a small but relevant guide with all the rules to be respected to contribute to OOo (what you are doing). That way, they could check everything before attaching the patch. I suppose it may also ease integrating patches to the trunk if the team doesn't need to modify every variable, class, object... cheers, -- Pierre-André Galmes Free Software consultant StarXpert - www.starxpert.fr 6, rue Eugène Varlin - 75010 Paris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
