Re: [boost] problems with the current boost's functional, projection_iterator

From: Mark Rodgers (mark.rodgers_at_[hidden])
Date: 2001-10-04 14:20:15

> what's the biggest problem, that there are many header for the same 
> or similar thing:
> functional.hpp, function.hpp, bind.hpp, compose.hpp, operators.hpp
> and it's seems to me there is not a common basic design decision behind
> the whole thing. everybody (like me) do what he would like to use and
> put into boost. IMHO it's high time to reconsider the whole thing
> and keep in mind the other parts of boost call_traits, type_traits, and
> iterator_adaptors to be consistent!

The problem is that we already have composers, but the just don't work
as well as they might.  The solution seems to me to be to fix the 
existing composers rather than create new ones.

I do agree that a refactoring is necessary.  It certainly seems that
the function traits from functional.hpp need to come out of there
into somewhere that compose.hpp can include them, and others might
find a use for them.  The nullary_function from compose.hpp would move 
there too.

Mark