STL or Write-Your-Own?

It be worth saving development time by using STL. And I don't know where you have heard that stl has alot of overhead and that slt are not suited for game development, because thats just not true.

Lizard

Use STL. Always. I do, and it has never hurt me. My bottlenecks are in my own code.

Reason: you posted in "for beginners", so you probably wont beat the compiler writers doing what they do best. I know I wouldn't be able to.

If it was easy to beat the STL, don't you think people would be using such a faster version as the standard?

Thanks, STL it is then :)

The C++ FAQ Lite has a good explanation of why you should use the container classes rather than writing your own.

Let's see... you can use existing code that has had a lot of testing and is quite well documented, or you could spend what could be quite a bit of time rolling your own solution which would then require extensive testing to ensure it was behaving as you expected.

Unless you're making your own implementation as a learning experience (it is quite a good excercise if you've got some spare time) always go with the Standard Library implementation; if you find that your resulting program is too slow and profiling reveals the overhead from a Standard Library container is at fault then you might consider trying to write a faster implementation.