Re: Justifying the GTK+ 3.0 ABI break

["Morten Welinder" <mwelinder gmail com>]

> Or maintaining a bunch of deprecated API?

I looked at the log for gtkclist.c and the majority of the changes over the
past five years are a direct consequence of the api having been declared
deprecated.  Specifically there is a lot of defining and undefining of
GDK_DISABLE_DEPRECATED going back and forth there.  Even so,
not much is going on.

So the maintenance burden, to the extent there is one, is _caused_ by
deprecation.  And that's even within gtk+.

Pretty ironic, isn't it?

Morten