On 12/2/2011 4:57 AM, Dave Abrahams wrote:

A few things I just noticed:

1. http://www.boost.org/doc/libs/release/libs/phoenix/doc/html/phoenix/what_s_n... says:

"Bind is no completely compatible with Boost.Bind"

There's a letter missing after "no," the choice of which ("w" or "t") can invert the meaning of the sentence! It wasn't until I got to http://www.boost.org/doc/libs/release/libs/phoenix/doc/html/phoenix/modules/... that I realized it was "w"!

This is already fixed in trunk

2. On the same page I think there's a messed up cross-reference, because

"phoenix.modules.function phoenix::function"

Doesn't make a whole lot of sense.

Fixed.

3. On libs/phoenix/doc/html/phoenix/starter_kit/values.html I see:

Confused? val(3) is a unary function, you say? Yes it is.

No, it isn't. val is a unary function. val(3) *invokes* a unary function.

Ok. Thanks for catching that.

4. libs/phoenix/doc/html/phoenix/starter_kit/lazy_operators.html says that

x[ref(i)]

is an error but it gives only a confusing partial explanation that doesn't seem to follow the rules above it. operator[] looks as much like a binary operation as operator*; the difference is that the former must be a member.

I see. Ok, I added some notes to make this clear.

5. Can we please, finally, *deprecate* Boost.Lambda and put a sign on its docs directing people to look at Phoenix?

I'm not sure who's in a position to do that. Regards, -- Joel de Guzman http://www.boostpro.com http://boost-spirit.com