Quote:Original post by howie_007
I think what you're really looking for is a singleton. I use them in my engine.
held by a smart pointer or such consideration is bogus?
Where would I new the singleton? in the Heap or stack?
Quote:Original post by howie_007
I think what you're really looking for is a singleton. I use them in my engine.
Quote:Original post by draconarQuote:Original post by howie_007
I think what you're really looking for is a singleton. I use them in my engine.
held by a smart pointer or such consideration is bogus?
Where would I new the singleton? in the Heap or stack?
Quote:Original post by davepermen
i'll correct myself asap. to my excuse: i'm not native English, and i slept only 4h this night.. :) (and i didn't had spell correction turned on English. now i have). shame on me.
Quote:Original post by BitMaster
Back in the days, STL had been proposed by SGI to be included in the C++ standard library. Large portions of it are now part of the C++ standard library but not everything and there are also parts which are part of the standard which were not part of STL.
I frequently catch myself using the name as well even though I do not better, the name rolls very easily off the tongue. But one should at least be aware that using it is not correct in the general case.
Quote:Original post by Antheus
It's OK, Microsoft is wrong too. They keep using the term STL in their documentation. So does IBM. And Intel. And everyone else.
Quote:Original post by Antheus
Personally, I'm happy if someone who lists 5+ years of in-depth C++ experience has:
- heard of STL
- used it
- really used it themselves (actually wrote some code)
- can actually list the basic few containers
- has programmed anything that was not C code compiled with C++ compiler
I have given up on trying to ask about:
- template programming (specialize a class)
- allocation techniques (how would you use a class that uses custom allocator)
- generic programming (algorithm.h, iterators, traits)
- boost (better left alone, the things people create with it are a disaster - they're better off using some other language)
So in practice, one ends up with something similar to Google's guidelines. C with classes.
Quote:Original post by draconar
But traits & template meta programming I still finding daunting and confusing for my level of expertise.
Quote:Original post by draconar
Actually, I thought that both shared_ptr & auto_ptr were only part of the tr1, not of the std alone.
Quote:Quote:Original post by Zahlman
(please do not say "STL"; that has not been a meaningful term for many years)
I don't get it. could you please elaborate?
Quote:
The Standard Template Library (STL) is a software library partially included in the C++ Standard Library. It provides containers, iterators, algorithms, and functors. More specifically, the C++ Standard Library is based on the STL published by SGI. Both include some features not found in the other. SGI's STL is rigidly specified as a set of headers, while ISO C++ does not specify header content, and allows implementation either in the headers, or in a true library.
Quote:Original post by davepermen
std::tr1 is the namespace for the next c++ standard (c++0x or something).
Quote:Original post by ZahlmanQuote:Original post by davepermen
std::tr1 is the namespace for the next c++ standard (c++0x or something).
No; tr1 is a revision to C++98, which was done in 2003. The full C++0X standard is rolling out now-ish.
Quote:Original post by SiCrane
You have TR1 and TC1 confused. Technical Corrigendum 1 is ISO/IEC 14882:2003, the 2003 update to the C++ standard. TR1 is ISO/IEC TR 19768, C++ Library Extensions, which is a non-normative set of proposed C++ standard library extensions, which, if implemented, live in the std::tr1 namespace.