[assign] documentation bug
In the assign library documentation page <boost>/libs/assign/doc/index.html#repeat: v = list_of(1).repeat(5,2)(3); // v = [1,2,2,2,2,2,3] BOOST_ASSERT( v.size() == 1 + 5 + 3 ); push_back( v )(1).repeat(1,2)(3); // v = old v + [1,2,3] BOOST_ASSERT( v.size() == 12 ); I think the first BOOST_ASSERT should be BOOST_ASSERT (v.size() == 1 + 5 + 1) and the last one should be BOOST_ASSERT( v.size() == 10 ); -- Caleb Epstein caleb.epstein@gmail.com
"Caleb Epstein" <caleb.epstein@gmail.com> wrote in message news:989aceac041107112759613c30@mail.gmail.com... | In the assign library documentation page | <boost>/libs/assign/doc/index.html#repeat: | | v = list_of(1).repeat(5,2)(3); | // v = [1,2,2,2,2,2,3] | BOOST_ASSERT( v.size() == 1 + 5 + 3 ); | | push_back( v )(1).repeat(1,2)(3); | // v = old v + [1,2,3] | BOOST_ASSERT( v.size() == 12 ); | | I think the first BOOST_ASSERT should be BOOST_ASSERT (v.size() == 1 + | 5 + 1) and the last one should be BOOST_ASSERT( v.size() == 10 ); yes, thanks! It's applied to the dev-branch. -Thorsten
On Sun, 7 Nov 2004 21:48:35 +0100, Thorsten Ottosen <nesotto@cs.auc.dk> wrote:
"Caleb Epstein" <caleb.epstein@gmail.com> wrote in message news:989aceac041107112759613c30@mail.gmail.com... | In the assign library documentation page
| <boost>/libs/assign/doc/index.html#repeat: | | v = list_of(1).repeat(5,2)(3); | // v = [1,2,2,2,2,2,3] | BOOST_ASSERT( v.size() == 1 + 5 + 3 ); | | push_back( v )(1).repeat(1,2)(3); | // v = old v + [1,2,3] | BOOST_ASSERT( v.size() == 12 ); | | I think the first BOOST_ASSERT should be BOOST_ASSERT (v.size() == 1 + | 5 + 1) and the last one should be BOOST_ASSERT( v.size() == 10 );
yes, thanks!
It's applied to the dev-branch.
So it is expected that this error is still in the 1.32.0 RC tarballs? -- Caleb Epstein caleb dot epstein at gmail dot com
Caleb Epstein writes:
On Sun, 7 Nov 2004 21:48:35 +0100, Thorsten Ottosen <nesotto@cs.auc.dk> wrote:
It's applied to the dev-branch.
So it is expected that this error is still in the 1.32.0 RC tarballs?
It's "expected" in the sense that since the change wasn't merged to the branch, there is no way it could get in the tarballs. But there is no good reason for it. Fixed. -- Aleksey Gurtovoy MetaCommunications Engineering
participants (3)
-
Aleksey Gurtovoy -
Caleb Epstein -
Thorsten Ottosen