Parapura Rajkumar wrote:
Quote:
int main(int argc, char* argv[])
{
std::map<int, int>::iterator footest;
{
std::map<int, intfoo;
foo[0] = 0;
footest = foo.begin();
}
return 0;
}
>
Is this undefined behavior? Please note that footest is going out of
scope before std::map.
|
You mean, "after 'foo'", don't you?
Quote:
In theory an implementation could have a
iterator destructor that could still access the std::map ?
|
No. The iterator is allowed to be invalid, that does not affect
its destruction.
V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask
iterator pointing to invalid container 
