Opened 14 years ago
Closed 13 years ago
#2691 closed Bugs (fixed)
typo in vector container concepts documentation
Reported by: | Owned by: | Gunter | |
---|---|---|---|
Milestone: | Boost 1.39.0 | Component: | uBLAS |
Version: | Boost 1.37.0 | Severity: | Cosmetic |
Keywords: | Cc: |
Description
In the second table of http://www.boost.org/doc/libs/1_37_0/libs/numeric/ublas/doc/container_concept.htm#vector, the phrase:
array_type& if a is mutable
should read:
array_type& if v is mutable
Change History (8)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
The corresponding line in the matrix concepts table has the same problems. Here, a has to become m (not v).
comment:3 by , 14 years ago
Component: | None → Documentation |
---|---|
Owner: | set to |
comment:4 by , 14 years ago
Component: | Documentation → uBLAS |
---|---|
Owner: | changed from | to
comment:5 by , 14 years ago
comment:6 by , 14 years ago
Status: | new → assigned |
---|
comment:7 by , 14 years ago
Milestone: | Boost 1.38.0 → Boost 1.39.0 |
---|
merged changes into release branch
comment:8 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
The concepts for "immutable" and "mutable" classes will be handled in task #3188.
Note:
See TracTickets
for help on using tickets.
Actually, the entire line of the table is messed up. Under "Type requirements", it says:
v is mutable and Dense.
Under "Return types" it says (with v replacing a):
array_type& if v is mutable, const array_type& otherwise
But v is required always to be mutable so the otherwise case makes no sense. The type requirement should be just that v is dense.