std::map iterator difference between (*pos).second and pos->second

Asked Jun 27 '16 at 16:52

Active Jun 27 '16 at 16:52

Viewed 52 times

I have some legacy code which uses (*pos).second to get a structure:

std::map<std::string, TMyStruct> TMyStructMap;

TMyStructMap  infoMap;
TMyStructMap::const_iterator pos = infoMap.begin();

// then later somewhere

TMyStruct x = (*pos).second;

Isn't this the same as: TMyStruct x = pos->second ?

If so, any advantage or style reason for doing one over the other?

asked Jun 27 '16 at 16:52

Danny

2,482
3
34
48

@Wikiti C has no iterators afaik – 463035818_is_not_an_ai Jun 27 '16 at 16:55
3

@Wikiti I would agree except the operators can be overloaded in C++ so the behavior could be different. I would expect them to be the same in any sane implementation though. – NathanOliver Jun 27 '16 at 16:56
@NathanOliver You're right. Unless `->` and `*` are overloaded, the behaviour should be exactly the same. – Wikiti Jun 27 '16 at 16:57
@NathanOliver your statement isn't strong enough. If `* .` and `->` behave differently, the implementation is broken. – Mark Ransom Jun 27 '16 at 17:12

std::map iterator difference between (*pos).second and pos->second

0 Answers0