Re: bind and shared_ptr

2010-05-07 Thread Peter Kümmel
Pavel Sanda wrote: > Peter Kümmel wrote: >> We often have 'using namespace std' in our code and msvc10 makes bind >> visible as std::bind, this generates many conflicts. And why should >> we use third party code when the compiler comes with it's own >> implementation? >> >> Using tr1 also prevents

Re: bind and shared_ptr

2010-05-07 Thread Peter Kümmel
Vincent van Ravesteijn - TNW wrote: >>> I agree with killing boost, but we should do it cleanly. We could >>> start with the headers as Peter suggested and use tr1 for everybody. >>> Then if there are problems, we'll add exceptions for some computers. >>> Or we can do autoconf/cmake tests on the

RE: bind and shared_ptr

2010-05-07 Thread Vincent van Ravesteijn - TNW
>> I agree with killing boost, but we should do it cleanly. We could >> start with the headers as Peter suggested and use tr1 for everybody. >> Then if there are problems, we'll add exceptions for some computers. >> Or we can do autoconf/cmake tests on the features. > >fine with me if this will

Re: bind and shared_ptr

2010-05-07 Thread Pavel Sanda
Jean-Marc LASGOUTTES wrote: > I agree with killing boost, but we should do it cleanly. We could start > with the headers as Peter suggested and use tr1 for everybody. Then if > there are problems, we'll add exceptions for some computers. Or we can > do autoconf/cmake tests on the features. fine wi

Re: bind and shared_ptr

2010-05-07 Thread Jean-Marc LASGOUTTES
Pavel Sanda writes: > from what i remember we tried to kill boost on last dev meeting and replace > it by tr1, but the whole business was canceled because some ms compiler stop > to work. maybe its no more trouble. also some regexp routines are not > fully compatible in tr1 iirc. but killing boost

Re: bind and shared_ptr

2010-05-07 Thread Pavel Sanda
Peter Kümmel wrote: > We often have 'using namespace std' in our code and msvc10 makes bind > visible as std::bind, this generates many conflicts. And why should > we use third party code when the compiler comes with it's own > implementation? > > Using tr1 also prevents the including of myriads o

Re: bind and shared_ptr

2010-05-07 Thread Peter Kümmel
Jean-Marc LASGOUTTES wrote: > Peter Kümmel writes: > >> Because we get trouble with bind and shared_ptr coming with boost and >> msvc10 I've introduced support/bind.h and support/shared_ptr.h where >> I've moved both functions into the lyx scope and where we can switch >> between the usage of boo

Re: bind and shared_ptr

2010-05-07 Thread Jean-Marc LASGOUTTES
Peter Kümmel writes: > Because we get trouble with bind and shared_ptr coming with boost and > msvc10 I've introduced support/bind.h and support/shared_ptr.h where > I've moved both functions into the lyx scope and where we can switch > between the usage of boost and tr1. > Currently I only use f