I really want to give my approval, for what it is worth... I vote to accept Phoenix into Boost. However, I think it is important to keep Boost.Bind as many of Boost users don't know (yet) Phoenix but intensively use Bind, that's to say they only use Bind because they just need it, no more. The documentation is excellent - I had to use it for some personal projects - and I got used to Phoenix very quickly. The syntax is quite simple compared to the work done in background by the library. Thank to Phoenix, we can now write FP code in C++ quickly, efficiently. Thanks guys.
Alp Mestan wrote:
I really want to give my approval, for what it is worth...
I vote to accept Phoenix into Boost.
Thank you, Alp.
However, I think it is important to keep Boost.Bind as many of Boost users don't know (yet) Phoenix but intensively use Bind, that's to say they only use Bind because they just need it, no more.
No worries. Bind is not going away.
The documentation is excellent - I had to use it for some personal projects - and I got used to Phoenix very quickly. The syntax is quite simple compared to the work done in background by the library.
Thank to Phoenix, we can now write FP code in C++ quickly, efficiently. Thanks guys.
Most welcome. Regards, -- Joel de Guzman http://www.boostpro.com http://spirit.sf.net
participants (2)
-
Alp Mestan -
Joel de Guzman