On Thu, Dec 17, 2009 at 9:34 PM, Hartmut Kaiser
IIRC, Phoenix was reviewed and accepted on the condition that it be reimplemented on top of Proto. That hasn't happened yet, and so Phoenix has not been merged to trunk. The old version of Phoenix still exists as a part Spirit.
Hasn't this effort demonstrated that phoenix might not be as portable as the current implementation?
What effort?
Why do you think Phoenix isn't 'portable'? Do you mean it doesn't compile on outdated compilers? Or do you mean it doesn't compile using C++0x? What do you mean by that? Please be more specific.
I meant what Eric commented on the MSM thread about MSVC (8 and above) bugs w.r.t proto. Though I have to say the only bug in MSVC for proto I found has a very specific workaround in proto documentation. I do use proto in some of my projects. I'll try to find the specific message and quote it.
Maybe isn't the current implementation good enough for Phoenix to be a first-class citizen?
I'm not sure where this comes from. If you followed the review or read the review decision you wouldn't ask this question.
Sorry. I really didn't. Though I really wanted phoenix to be a first-class library in boost. Not to be found only inside Boost.Spirit v2.
Regards Hartmut
Regards, -- Felipe Magno de Almeida