|
Boost : |
Subject: [boost] Phoenix documentation problems
From: Dave Abrahams (dave_at_[hidden])
Date: 2011-12-01 15:57:40
A few things I just noticed:
1. http://www.boost.org/doc/libs/release/libs/phoenix/doc/html/phoenix/what_s_new/phoenix_3_0.html
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/bind/compatibility_with_boost_bind.html
that I realized it was "w"!
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.
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.
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.
5. Can we please, finally, *deprecate* Boost.Lambda and put a sign on
its docs directing people to look at Phoenix?
-- Dave Abrahams BoostPro Computing http://www.boostpro.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk