Team work (Score 1)

I work for a large firm (~800 employees) of which about 30 are full time software professionals.

I find that one major issue with using STL is that is not part of the C++ "language". That means that someone who says he/she knows C++ does not necessarily know STL.

This means that I have to avoid using the STL when my code is likely to be modified, read, fidddled with etc by other folk on the team.

This gets done qutie a bit and more importantly will be done when I leave the firm ...

In the case of say Perl or LISP (which admittedly do not compare directly) you get Hashes and Lists as part of the language itself.

Thus anyone who says he/she knows Perl /LISP knows about lists and hashes. They can be ued in peace.

Further having a list/hash as part of the language itself would possibly mean a significant reduction in the size/style of error messages and the like.

I still use the STL whenever I can and hide behind interfaces (when they can be well defined in advance) or when working on small individual projects.

While I cannot say this with any real confidence, I think that understanding why someone's chosen to use container x and not why .... i not well commented .... is hardly transparent either.