Re: gtkmm and boost

[manphiz <manphiz gmail com>]

Murray Cumming wrote:
> Boost is not a stable API. If it ever declares API and ABI stability
> then we could use it. Using boost now would break already-installed
> applications and break compilation of applications when boost is
> upgraded. 
>
> When parts of the Boost API become part of the official C++ standard
> then we would use that API where appropriate. For instance, we hope to
> port to a standard C++ signals API in the future. That API was largely
> based on libsigc++ anyway. 

Though there are some libraries staying intact for quite a long time 
already, I agree with you on Boost's unstable nature. But it hurts me 
when some part of gtkmm and Boost provide different interfaces, most 
significantly incompatible smart pointers.

However, it seems at least TR1 is in a more stable status now, though 
several amendment is being revised and voted according to the C++ 
standard working groups. So is it possible to import TR1 stuff into 
glibmm once it is settled which covers some aspects in glibmm as smart 
pointer, regex, reference wrapper, omnibinder? Maybe it's reasonable to 
wait for wider compiler support though :)