Re: Recommended way to handle deprecation?
"muppet" <[email protected]>
| Newsgroups | gmane.comp.gnome.language-bindings |
|---|---|
| Message-ID | <[email protected]> |
Andreas Rottmann said: > I wonder what the recommended way to handle deprecated API: to wrap or > not to wrap, that's the question here :). How do other bindings handle > this and is there a "recommended way"? gtk2-perl's Glib and Gtk2 modules explicitly do not bind things that were deprecated as of 2.0.0 (although some made it in by accident early on). Things that were deprecated during the 2.x series cannot be removed or the backward compatibility of the 2.x series would be lost, so thing deprecated *during* the 2.x series are left alone. For example, GtkCList was deprecated in 2.0.0, so it is not bound[1]; GtkOptionMenu was deprecated in 2.4.0, so we didn't do anything about that. [1] There's a separate, unofficial module that binds the deprecated widgets to ease porting from Gtk-Perl (gtk+ 1.x) to Gtk2-Perl (gtk+ 2.x). -- muppet <scott at asofyet dot org> _______________________________________________ language-bindings mailing list [email protected] http://mail.gnome.org/mailman/listinfo/language-bindings