This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] for tr1 progress documentation.


On Fri, Jan 20, 2006 at 11:02:17AM +0100, Paolo Carlini wrote:
>     2- I think it would be a mistake giving the impression that the
> point is ""adding stuff from SGI and Boost"". Indeed, Matt Austern, for
> instance, when preparing the specifications of the new unordered
> containers had very clear in mind the example of hash_map/has_set;
> likewise, we all know that many facilities in TR1 have been proposed by
> members of the Boost community. However, with the partial exception of
> shared_prt, all the implementation we are offering are completely
> unrelated to those codebases (i.e., the original HP/SGI STL, Boost) and
> in the end the real, "official", reference for the users of libstdc++-v3
> is TR1, nothing else. I think we have only two choices: either we say
> nothing about history, or, preferred, we say a minimum about it (thus
> mentioning the hashed containers in the original STL, Boost) but we
> carefully avoid conveying misleading messages.

Shared_ptr has to mention Boost, but as the source of ourimplementation,
not std::tr1::shared_ptr in general.  I see no need for any other part
to refer to Boost, nor to mention the hash_xxx containers unless it is
simply to say "the unordered_xxx containers are suitable replacements
for the non-standard hash_xxx containers in the SGI STL" (with a link to
ext/howto.html)  i.e. mention them as redundant, not as the inspiration
for the new classes.

jon


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]