Re: Is CArray best for this...
David Ching wrote:
Nothing is missing, but what is there appeals to computer scientists and not
necessarily to the domain-specific sensibilities of Windows app developers.
Iterators have strange syntax, some STL construct (forget which one) needs
to reference ".first" and ".second" is totally bizarre, etc. This is
completely acceptable, and even desireable, for computer scientists, but not
for app writers who are not interested in becoming experts in collections
per se, only in that they allow them to write their apps.
Strangely enough, I wrote the following piece of code just yesterday
typedef std::map<CString, CString> StringMap;
for (StringMap::const_iterator it = m_itemMap.begin(); it != m_itemMap.end();
You see MFC and STL playing nicely together. Yes, you need to know that
iterators are like pointers to the elements, and that the elements of std::map
are std::pair<Key, Value>, but what is so strange or bizarre about that?
As Norbert says, the concepts used (here iterators and std::pair) are universal
to the STL, unlike with CMap, which uses member functions and a nested class
CPair that are unique to CMap.
CMap also suffers from the fact that the template arguments ARG_KEY and
ARG_VALUE cannot be defaulted to the sensible const KEY& and const VALUE&
because the arguments are in the wrong order. I have never understood what the
purpose of the double (here quadruple) template argument was, and it was a
source of great confusion to me at the beginning.
But we might have to agree to disagree here ...
Visual C++ MVP