FreeLists / haiku-development / [haiku-development] Re: coding style

["Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>]

"Michael Lotz" <mmlr@xxxxxxxx> wrote:
> Anyway, as we simply do not agree, it is pretty pointless to argue 
> over 
> it. As we disallow the double variable declaration "char *variable1, 
> *
> variable2;" per the style guide as well, there is nothing technically 
> preventing either style. The question is how do we proceed from here? 
> Should we cast a vote or do we simply agree on the compromise you 
> proposed and write that down to the style guide? I think one can get 
> used to pretty much everything, so I can live with "char*" as well 
> (but 
> I still find it ugly :-)).

I dunno. Actually, I think "char* a" and "char *a" don't look 
completely different as long as they are used consistently in one 
module, even though I find the former more appropriate and less 
confusing.

So how about just another compromise: we use "char* a" in public C++ 
headers, and respect the maintainer's choice of that in modules to make 
sure it's used consistently? That's at least better than what we have 
now :-)

Bye,
   Axel.