On 3/17/2011 5:51 PM, Thomas Heller wrote:
Hi all,
The next boost release is nearing and I want to include Phoenix. However, there are some questions that needs to be solved.
How to deal with Boost.Bind and Boost.Lambda? First of all, I don't think its a good idea to remove either of those. However, should Phoenix deprecate Boost.Bind and Boost.Lambda?
Phoenix should not deprecate anything. Boost will probably decide to deprecate Boost.Bind and Boost.Lambda eventually. Getting Phoenix into Boost for 1.4.7 is right now most important.
If yes, how should this deprecation be handled? My main concern is that most users will just continue to use BB and BLL just because of their names.
So they do. It's not breaking Phoenix if that happens, is it ? If Phoenix is better it will be used. There is no need to pull the rug from Bind or Lambda to force end-users to change, or even worry about it now. If and when that change happens Boost can always look to switch end-users from Bind and/or Lambda in the future by not supporting those libraries anymore and/or pulling them from the Boost distribution.
What about Phoenix V2? For V2 I have a clearer vision. I would like to have three phases: 1) Have V2 and V3 coexist in the tree, have a macro that decides which version should be included. will default to V2 2) deprecate V2, change the default of the macro introduced in 1) to V3 Alternatives: 3 a) remove phoenix v2 3 b) move phoenix v2 to another namespace so that V3 and V2 don't interfere anymore
Either 1 or 2, but just document it. C'mon Thomas and Phoenix developers, get Phoenix into 1.4.7 with proper documents about it and how to use it, and worry about Bind, Lambda, and Phoenix 2 some time later. There will be plenty of time for that once Phoenix officially gets into Boost and developers, like me, start using it who would not have done so before because it was never officially a Boost library and finding its documentation and how to use it was nearly impossible.