Skip to main content
gamedev.net
🔒 Locked

STL problems...

Started by mrmrcoleman 4 replies 550+ views
Original Post
mrmrcoleman
mrmrcoleman
I have recently moved my project away from UNICODE for various reasons. I have now noticed a few errors in the STL sections of my code, for example reference vector.end() causes an error so I have to use end()-1. Also push_back is now causing an error... Has anybody heard of this before? Thanks for any advice. Mark Coleman
darookie
darookie
Sounds odd. Did you do a full rebuild of your project? It could be that the object code of some components is still UNICODE and therefore causes memory corruptions due to the different value size (applies to strings only).
mrmrcoleman
mrmrcoleman
Hmm, I did a full rebuild but I still have the same problem. However a bit of digging around reveals that push_back is actually working elsewhere in the program... I will have to look at this more closely.

Thanks for the suggestion darookie.

Kind regards.

Mark Coleman
darookie
darookie
You're welcome!

Best regards,
Pat.
Enigma
Enigma
Quote:
Original post by mrmrcoleman
...reference vector.end() causes an error...

Do you mean doing:
std::vector<Type>::iterator iterator = myVector.end();iterator->function();

or
std::vector<Type>::iterator iterator = myVector.end();function(*iterator);

?
Both of these are errors. vector.end() returns an iterator one past the end of the vector, so vector.end() - 1 is the last element in the container.

Enigma
mrmrcoleman
mrmrcoleman
Enigma...

Yes, I looked bacl through my code and it was indeed missing a -1. I am having a hard day!

Mark Coleman

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.

Sign in to reply to this topic.