🔒 Locked

Microsoft STL bugs

Started by J-Baby Jan 2, 2004 at 2:46 PM 8 replies 1.2k views

Original Post

Jan 2, 2004 at 2:46 PM

Hi all, I noticed on the O.G.R.E. homepage that they state that the Microsoft VC++ version 6 STL library " ... has a number of known bugs" (the URL is http://www.ogre3d.org/docs/FAQ.html if you want to read it). Are these bugs documented anywhere or is it better to just to do what they did and use the STLport library instead of the MS STL implementation? Thank you, John

shurcool

109

shurcool

Jan 2, 2004 at 3:14 PM

Either use VS.net, or visit this page.

To give you an example of what kind of problems VC6 can give you (although this specific example has to do with std streams, it's the same kind of thing), take a look at this thread.

Or just try compiling this code in VC6:

#include <iostream>
#include <stdlib.h>

class Universe
{
public:
	Universe() { std::cout << "Universe created." << std::endl; }
	~Universe() { std::cout << "Universe destroyed." << std::endl; }
};

Universe *theUniversePtr;

void Destroy()
{
	delete theUniversePtr;
}

int main()
{
	theUniversePtr = new Universe();

	atexit(&Destroy);

	return 0;
}

---
shurcooL`

[edited by - shurcooL on January 2, 2004 4:18:40 PM]

Arild Fines

138

Arild Fines

Jan 2, 2004 at 4:02 PM

To be fair, the STL shipped with VC6 wasn''t written by Microsoft - it was licensed from Dinkumware.

Kylotan

Mod

3,487

Kylotan

Jan 2, 2004 at 5:36 PM

shurcool

109

shurcool

Jan 3, 2004 at 10:33 AM

Kylotan, that was my solution until I finally got VS.NET!

Boy, am I ever so happy. At least compiler-wise.

---
shurcooL`

thebolt00

Jan 3, 2004 at 11:44 AM

quote:
Original post by Arild Fines
To be fair, the STL shipped with VC6 wasn''t written by Microsoft - it was licensed from Dinkumware.

So is the STL shipped with VC.NET, and Dinkumwares STL is really nice IMO. The problem with VC6 isn''t directly related to Dinkumwares implementation, but to the fact that VC6 have alot of problems with templates (no, i don''t have a source for that, but its easy to run into "INTERNAL COMPILER ERROR" when you do for example template specialization with VC6)

Jenison

Jan 3, 2004 at 2:57 PM

IIRC microsoft took a slice of it ...

the current Dinkumware is pretty good. I did testing on the current library about a year ago vs Microsofts copy for a very large company who wanted to remove MS STL from their code. Needless to say the current was a bit faster

[edited by - Jenison on January 3, 2004 3:58:17 PM]

Hazelnuss

Jan 4, 2004 at 9:54 AM

Are those bugs fixed after installing the current VS6 Service Pack?

Jan 5, 2004 at 2:27 AM

Interestingly, if I use stlport then it leaks in mfc while dinkum''s doesn''t. Anyone with stlport seen this as well?

vector v;
v.push_back(new int(5));
delete v[0];

you should get unknown leak of 320 bytes. Maybe it has to do with stl memory allocations in ways that doesn''t make mfc happy.

Topic Locked

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