problem with deque in stlport 5

[vajagic]

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?

[Jerry Coffin]

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.