-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/8/2005 6:08 AM, Kristian Rietveld wrote:
> I assume that there isn't much code out there using the GtkFileSystem API.
> In order to not have that kind of code crash and burn on a system with a newer
> GTK+, we need to build in some kind of protection. Does anyone have
> suggestions on this one?
Why not keep the current API and invent a new one for async operation?
Use gtk_file_system_async_foo() and the like, and just deprecate the
current API. If you install a header file to a public system location,
no matter what you say, it's a public interface. If you want to change
that API incompatibly, you're obligated to increment gtk's major
version. IM(NS)HO, of course.
-brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFDcQNp6XyW6VEeAnsRAmEyAJ0d22ACUMDUufb23jtNxO94l+PGtACfSxj8
yPxEUoo1NclyaA/JNRd/7n4=
=EMPS
-----END PGP SIGNATURE-----
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list
