Re: [boost] [optional] library documentation typo

From: Martin Bonner (martin.bonner_at_[hidden])
Date: 2005-07-07 08:40:40

----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.

-- 
Martin Bonner
Martin.Bonner_at_[hidden]
Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ,
ENGLAND Tel: [phone]