On 20.01.09 21:29:48, Alexander Neundorf wrote:
> On Monday 19 January 2009, Andreas Pakulat wrote:
> > On 18.01.09 23:33:21, Andreas Pakulat wrote:
> ...
> > > > The problem with that is when a new version is out.
> > >
> > > Not really, if a project uses boost, one of its dev should _check_ that
> > > it still works with the newer version (As I said in the other mail,
> > > kdevplatform for example doesn't build with 1.37). And if he verified
> > > that, he can simply commit the change.
> > >
> > > IMHO you can't assume that your boost-using project will work just fine
> > > with a newer version.
> 
> Are they that bad with keeping compatibility ?

I don't have that much long-time experience and kdevplatform/teamwork
compiles just fine with 1.33, 1.34 and 1.35, but I think maybe part of the
problem is that its a template library and hence keeping BC/SC is
relatively hard, so they simply don't try at all or just can't. 

Andreas

-- 
Give your very best today.  Heaven knows it's little enough.
_______________________________________________
Kde-buildsystem mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-buildsystem

Reply via email to