Re: First deprecate APIs and then remove them in the next major version

On Thu, Dec 14, 2017 at 08:02:56PM +0100, Bastien Nocera wrote:
On Thu, 2017-12-14 at 19:56 +0100, Sébastien Wilmet wrote:

With "soft API breaks" (i.e. just removing an API that was deprecated
a previous major version), I think this would improve a lot the
situation and would avoid to repeat the same problem as GTK+ 2 -> 3.

It already exists. Look at the "DISABLE_DEPRECATED" macros in the
current version of libraries, and which usually get removed in the +1

Yes, it's a nice feature, but it doesn't solve the problem that there
are a lot of direct API breaks during GTK+ 3.9x development.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]