> When GTK+ breaks the API, it doesn't mean that a higher-level library > needs to break API too.
That depends. You are right that a lot of API changes can be hidden. But if the higher-level library has an API that includes a type which is being removed, then the API will have to be changed. And if your library depends on a feature that is being removed then your library probably cannot be saved with an API break. M _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
