By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,044 Members | 1,291 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,044 IT Pros & Developers. It's quick & easy.

problem with deque in stlport 5

P: n/a
In stlport 4.xx inserting in deque worked like this:

itCurr = m_deqCoord.insert(itCurr, nValue);

itCurr was set to the new element. But in stlport this is not the case.
Is this a bug or it is by design or something else?

Sep 18 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
In article <11**********************@k70g2000cwa.googlegroups .com>,
va*****@gmail.com says...
In stlport 4.xx inserting in deque worked like this:

itCurr = m_deqCoord.insert(itCurr, nValue);

itCurr was set to the new element. But in stlport this is not the case.
Is this a bug or it is by design or something else?
It sounds likea a bug to me. According to the standard, ($23.1.1/6):
"The iterator returned from a.insert(p,t) points to the copy of t
inserted into a."

--
Later,
Jerry.

The universe is a figment of its own imagination.
Sep 18 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.