Forte and the STL

Question

Hello all,
I have a question regarding fortes compliance with the standard regarding the STL. Does it.
For example, just trying to compile simple code such as...
#include <memory>
int main(void)
std::allocator<char> a;
char *p;
a.destroy(p);
return 0;
Will not compile (ignore that the code is bad). The error msg comes back with destroy not a member of std::allocator. Checking my trusty copy of the standard it sure should be. What is going on? There are other places that the header files do not seem to be inline with the standard ie reverse_iterator<> (one template param of type iterator).
Thoughts?
Any help would be great because I'm not sure I can use forte if it is missing huge chunks of the standard.
Mike

Answer 1

Thanks for the response but I'm not sure what your suggesting,
Is it to use destroy() instead? If so then I still have the same problems-changing lots of code to support a non-conforming compiler. Or do you think that destroy() is the code that I'm using? I'm referring to std::allocator<T>::destroy() found in ISO 14882 [lib.default.allocator] (pg. 369) and in The C++ Programming Language (pg 567) Since you quoted me page numbers on the other post :)
I know this seems trivial but there are numerious places where forte seems to use a pre-standard implementation so changing it all becomes non-trivial fast-for example, the lack of support for partial template specialization (I think) causing them to apparently use the old version of std::reverse_iterator.
Mike