At 1243440797 time_t, koniu wrote: > And maybe more. The problem is that these functions are bound to be > explicitly used by some users and this would be breaking API (again). > We could of course deprecate them to make the process smoother but > still. In fact, there's a lot more in the namespace that could be > unified - think awful.tag.getproperty vs awful.client.property.get - > at what stage would we be cleaning all of this up?
I agree with you. From my point of view, this is only the top of the iceberg. The thing is that we do not have a real naming convention, even in the core, there's things very weird: image_getwidth() window_state_get() ewmh_window_icon_get_reply() So, for unification we should do it ASAP, but first, we should make a clear decision, written in marble and in STYLES, about how we name things. Then, all changes should be done with deprecation warnings and should not break anything. We broke enough things on each release because it's sometimes hard to maintain backward compatibility, but as for name changes, that's very easy. (So for your patch, tell me if you want me to merge it right now or if you want to rename the function now.) Cheers, -- Julien Danjou // ᐰ <[email protected]> http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // In the Sixth Sense, Bruce Willis is dead.
signature.asc
Description: Digital signature
