Boost logo

Boost :

Subject: Re: [boost] Phoenix as a Boost library
From: PB (newbarker_at_[hidden])
Date: 2010-10-14 10:32:06

On Thu, Oct 14, 2010 at 3:02 PM, Thomas Heller
<thom.heller_at_[hidden]> wrote:
> PB wrote:
>> On Thu, Oct 14, 2010 at 4:22 AM, Edward Diener <eldiener_at_[hidden]>
>> wrote:
>>> On 10/13/2010 10:50 PM, Joel de Guzman wrote:
>>>> On 10/14/2010 10:41 AM, Edward Diener wrote:
>>>>> I am curious to know if Phoenix will ever be released as a Boost
>>>>> library, or is it meant
>>>>> to be forever coupled with Spirit ?
>>>>> I have avoided it because it has never been released separately or had
>>>>> its documentation
>>>>> appear among the list of Boost libraries. I got the impression that it
>>>>> would be released
>>>>> separately, and expected to see it in Boost 1.44, but evidently that
>>>>> did not happen.
>>>> Thomas Heller completed the Proto port last July. Now the next
>>>> step is to have a mini-review. Then, Boost integration, IFF it
>>>> passes the mini-review.
>>> Thanks ! I am sure I am not the only one looking forward to seeing it as
>>> a library of its own, and using it, if it passes the mini-review.
>> Me too! There's something holding me back conceptually using Phoenix
>> in contexts where no Spirit parsing is actually taking place.
> Is it just because you need to include header from a spirit subdirectory?

In a nutshell, yes. I will just use it when I properly learn it. I've
only done some mild Spirit semantic actions with it so far. Other team
members who don't follow Boost at all (it's left to me here pretty
much) will also get confused when they see Spirit headers being
included and no apparent parsing taking place. With it not being a
top-level library, they can't quickly get documentation on it either.
I know where to dig to get it.



Boost list run by bdawes at, gregod at, cpdaniel at, john at