Daniel Rahn <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Sat, 29 Mar 2008 10:03:39 +0100:
> I guess the right thing to do is to come up with a glib-compat.h > containing the hack from bugzilla and then include that glib-compat.h > where up to now the single includes are done. That will also ease > maintenance of glib compatibility. > > Somehow I tend to think API breakage may appear in glib any time again. Given the observation that 2.12 <> 2.14 <> 2.16 in that regard, that seems likely, yes. (Observation that I really haven't a clue not withstanding. =8^) Of course, the other possibility, since according to the comment the only thing used from glib is g_assert, would be to internalize an implementation of that and forget about attempting to keep up with the glib API entirely. But that brings its own baggage in terms of keeping up with any security updates and the like, baggage I'm sure you're all too familiar with in other contexts. So at least for now, keeping up with the glib API seems the thing to do. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman _______________________________________________ Pan-users mailing list Pan-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/pan-users
