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

From: Bastien Nocera <hadess hadess net>
To: Sébastien Wilmet <swilmet gnome org>, Christian Hergert <christian hergert me>
Cc: gtk-devel-list gnome org
Subject: Re: First deprecate APIs and then remove them in the next major version
Date: Thu, 14 Dec 2017 20:02:56 +0100

On Thu, 2017-12-14 at 19:56 +0100, Sébastien Wilmet wrote:

<snip>

With "soft API breaks" (i.e. just removing an API that was deprecated
in
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
version.

Follow-Ups:
- Re: First deprecate APIs and then remove them in the next major version
  - From: Sébastien Wilmet

References:
- First deprecate APIs and then remove them in the next major version
  - From: Sébastien Wilmet
- Re: First deprecate APIs and then remove them in the next major version
  - From: Christian Hergert
- Re: First deprecate APIs and then remove them in the next major version
  - From: Sébastien Wilmet

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