[haiku-development] Re: Rename ControlLook constants, conflict
- From: "Adrien Destugues" <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 26 Oct 2017 08:19:04 +0000
26 octobre 2017 10:14 "Stephan Aßmus" <superstippi@xxxxxx> a écrit:
I know it can be a bit annoying having to specify the namespace. But there
are ways around that
which can sometimes be used. But polluting the global namespace with all
sorts of constants that
are actually relevant only in a certain context is even more annoying and can
cause even more
problems.
I agree with Looncraz that BControlLook::LEFT_ARROW is more elegant. Don't
know why I didn't go
with that.
We can rename the constants. Since the values are inlined in code which uses
them, it will not even break the ABI (only the API).
So, let's go for that, it at least avoids some confusion with identically named
constants elsewhere.
--
Adrien.
Other related posts:
- » [haiku-development] Rename ControlLook constants, conflict- John Scipione
- » [haiku-development] Re: Rename ControlLook constants, conflict- Adrien Destugues
- » [haiku-development] Re: Rename ControlLook constants, conflict- John Scipione
- » [haiku-development] Re: Rename ControlLook constants, conflict- looncraz
- » [haiku-development] Re: Rename ControlLook constants, conflict- John Scipione
- » [haiku-development] Re: Rename ControlLook constants, conflict- Stephan Aßmus
- » [haiku-development] Re: Rename ControlLook constants, conflict - Adrien Destugues
- » [haiku-development] Re: Rename ControlLook constants, conflict- Kacper Kasper
- » [haiku-development] Re: Rename ControlLook constants, conflict- Axel Dörfler
- » [haiku-development] Re: Rename ControlLook constants, conflict- Adrien Destugues