Point 1: I did not put in a bug report for this, since you do not see this normally, so won't "obstruct" your work. Thank you for pointing this out, though.
Point 2: I have put in a bug report for this:
case=42159
VA does not seem to support arrays defined by typedefs.
Point 1: I can forget pointing brackets and use dot by mistake. In this case VA supports my mistake showing listbox with std::map members. But I'm also not sure whether this is a serious bug or a bad feature :)
Point 2: I see the same effect even in case of declaration without typedefs: std::map<LPCSTR, RECT> namedrects[3];
I don't know what is the bug behind case=24414 but anyway I hope all these 3 points are related to one bug :)
Point 2: I am seeing this with VC6 SP6 and VA 1819:
which seems to be the good list (I get the same list when type std::map::|). I've created a new win32 test project. Do you see a different list in a new project?
Point 2: I'm seeing the same result as you see. The list is good in case of new project. But still I see a wrong list for Point 3 (e.g. namedrects[0]["key"].|): it consists of the same std::map members instead of RECT ones.
Arrays parsing in C++
Posted - Apr 08 2010 : 09:29:07 AM
