[boost] Re: [review] Formal review of the Smart Containerlibrarystarts today]

From: Thorsten Ottosen (nesotto_at_[hidden])
Date: 2004-10-04 04:28:19

"Thorsten Ottosen" <nesotto_at_[hidden]> wrote in message
news:cjq68v$2kv$1_at_sea.gmane.org...
| "Pavol Droba" <droba_at_[hidden]> wrote in message

| | Other small issues:
| |
| | * CloneManager::operator().
| |
| |   I don't like this notation. I would prefer something more explicit. I
see
| no clear connection
| |   between this operator and the operation it provides.
| |
| |   Also I don't understand the asymetry between CloneManager::clone
function
| and operator().
| |   Former is static, while the later is member function. Why?
|
| First, operator()() cannot be static.
|
| Second, operator()() is provided because a clone manager act as a deleter
| passed to the internal move ptr
| and other classes.

thinking about this makes me realize that it is probably wrong to specify
::clone()
as static; in the case of a stateful CloneAllocator, we probably don't want
that.

-Thorsten