[haiku-development] Re: Coding style conflicting with API
- From: pulkomandy <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 18 Nov 2012 12:43:18 +0100
On Sun, Nov 18, 2012 at 12:47:52PM +0100, Jonathan Schleifer wrote:
> Hi!
>
> The Haiku coding style says to use kSomeConstant instead of SOME_CONSTANT.
> However, BeOS used B_SOME_CONSTANT. Does this mean new APIs will have
> kBSomeConstant instead of B_SOME_CONSTANT?
Yes. Uppercase looks very 1980, and Be didn't do everything right.
So, all R5 constants stay with B_, and all new constants use k.
> Was the coding style taken from another project and it was simply forogotten
> that Haiku has different needs because it inherits the BeAPI, which forces
> the use of B_SOME_CONSTANT? Or will the API be broken with r2 and all
> B_SOME_CONSTANT chagned to kBSomeConstant?
The API will be broken in R2, and far beyond just renaming constants.
For now we'll have to live with the style mix for this.
--
Adrien.
Other related posts:
