Re: [boost] [optional] library documentation typo

From: Fernando Cacciola (fernando_cacciola_at_[hidden])
Date: 2005-07-08 18:24:08

"Martin Bonner" <martin.bonner_at_[hidden]> escribió en el mensaje 
news:E562FCEE3A42D61192880002A5FB433302D7AD0E_at_kite.pigroup.co.uk...
> ----Original Message----
> From: Felipe Magno de Almeida [mailto:felipe.m.almeida_at_[hidden]]
> Sent: 07 July 2005 13:55
> To: boost_at_[hidden]
> Subject: [boost] [optional] library documentation typo
>
>> 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
>
> Should be "optional<> does not have shallow-copy"
> Don't ask me to explain the logic behind the rules of English!
>
>> so does not alias: two
>> different optionals never refer to the same value unless T itself is
>> an reference
> Should be "a reference"
>
>>(but my have equivalent values).
>
> I agree, "(but may 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.
>
Thanks both Felipe and Martin!
Fixed now in CVS

Best

Fernando Cacciola
SciSoft