From: Felipe Magno de Almeida (felipe.m.almeida_at_[hidden])
Date: 2005-07-07 07:54:38
In the "The Interface" part, in the end of this text:
<quote>
For value access operations optional<> uses operators * and -> to
lexically warn about the possibliy uninitialized state appealing to
the familiar pointer semantics w.r.t. to null pointers.
However, it is particularly important to note that optional<> objects
are not pointers. optional<> is not, and does not model, a pointer.
For instance, optional<> has not shallow-copy so does not alias: two
different optionals never refer to the same value unless T itself is
an reference (but my have equivalent values).
</quote>
I think it should be:
(but may have equivalent values).
may in the place of my...
Thanks for boost and best regards,
Felipe.
-- Felipe Magno de Almeida Developer from synergy and Computer Science student from State University of Campinas(UNICAMP). Unicamp: http://www.ic.unicamp.br Synergy: http://www.synergy.com.br "There is no dark side of the moon really. Matter of fact it's all dark."