FreeLists / haiku-development / [haiku-development] Re: Coding guidelines

[Bruno Albuquerque <bga@xxxxxxxxxxxxx>]

Axel Dörfler wrote:
> > > For example, does all devs agree that private member _must_ start 
> > > with
> > > an underscore? Because it is not stated in the guidelines, but it 
> > > looks to me
> > > that some code does and some does not follow this guideline.
>>
> > And this reminds me that, although our code guidelines does state 
> > that, 
> > it is not a good practice and can lead to problems. For further 
> > information, I recomend this link (via Web Archive):
> > http://web.archive.org/web/19990221004617/http://www.ses.com/~clarke/cpptips/_naming
> We control the whole thing,
This is true today, yes, but won't always be true. Unless you expect we 
will never have any close-source libraries in the system at all.
> we don't port Haiku to somewhere else,
What do you mean with this? What about the PPC/M68k ports?

> and even if, it would be only a minor problem in C++ code anyway - 
> actually, only macros are problematic. But our naming conventions for 
> those are different anyway (uppercase).
> Also, there are no private but publically available macros.
>
> IOW we can safely ignore that article.
I beg to differ. I was bitten by this more than once. But then, again, 
this is just based on my own experience. This kind of stuff never happen 
to other people, right?
-Bruno