|
r=======================
Notes for STLport Users
=======================
Iterator Issues
---------------
The STLport library seems to use the identical
iterator type for both set and multiset, and also
an identical type for both map and multimap.
I could thus not come up quickly with an approach
that would guarantee a proper type qualification for
these iterators. Therefore, I decided to use a "generic"
name for both of the iterator types in the "set" family,
"gen_set<t>::iterator", and another generic name for
the map-family of iterators: gen_map<t>::iterator. By
using these names, the iterator policy code applies to
all iterators regardless of platform.
I suppose there's probably a way to have set iterators
be set<T>::iterator and multiset iterators be multiset<T>,
perhaps by scanning forward for the "multi" or lack of it;
however, this just seems kludgey because there may be *other*
types later on the line with "multi" in them and that
sort of special casing is just asking for trouble.
Debug mode: All "debug" iterators reduce to: "dbg_iter"
in debug mode.
VC7/.NET issues:
----------------
When using the STLport library with VC7, there are still
some issues with maps that I haven't completely figured out.
Consider this a "work in progress".
|
By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.
If a file you wish to view isn't highlighted, and is a text file (not binary), please
let us know and we'll add colourisation support for it.
This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.
A list of licenses authors might use can be found here
This member has not yet provided a Biography. Assume it's interesting and varied, and probably something to do with programming.