Talk:C++ Programming/STL

Note that the use of for_each which relies on a stateful functor is wrong, see http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#92 -- James Dennett (talk) 07:19, 4 September 2008 (UTC)
 * Nothing is wrong here. According to the 25.1.1/3 std::for_each applies functor "exactly last - first times. -- 95.220.2.63 (talk) 06:57, 19 August 2010 (UTC)
 * And if you are not still sure, please refer to boost.accumulators framework. It is based on stateful functors applied with std::for_each. -- 95.220.2.63 (talk) 06:59, 19 August 2010 (UTC)

Material on smart pointers is arguably misplaced, as they don't come from the STL. -- James Dennett (talk) 07:05, 16 October 2008 (UTC)

"Vector is known to be slow when using the MSVC compiler due to the SECURE_SCL flag" Does anyone have a citation for this? 129.59.129.167 (talk) 15:40, 29 December 2010 (UTC)


 * Checked Iterators at MSDN describes what SECURE_SCL does. Debug Iterator Support at MSDN describes what happens a bit more. Reading those two pages I can see that the SECURE_SCL flag causes extra checks to be done and I can see how those extra checks could cause Vector and other iterators to be slower compared to not using it. --dark lama  16:01, 29 December 2010 (UTC)

STL??
Just a note though, the term 'STL' is discouraged, as it is highly ambiguous. Are you referring to the entire C++ Standard Library? If so, say "Standard Library". Are you referring to the SGI STL? Are you referrring to the parts of the Standard Library based on the SGI STL? Are you referring to the Containers Library inside the Standard Library? Are you referring to a specific vendor's implementation of the entire Standard Library (e.g. libstdc++, libcxx, msvcrt.dll, ...) the parts of the Standard Library based on the SGI STL, or just the Containers Library?


 * Where did you got that idea ? (That STL referencing is discouraged) Is it simply your belief ?
 * I agree that it may be confusing (and IIRC I already had a discussion on this subject some time ago). I can agree with that but it is an historic artifact and as such it is not open to redaction (we can reduce the visibility or notoriety) but in this case it permits a clear distinction in regards to the learning the language, and it is a necessity for those that learned the language before the adaptation of the SGI STL into the standard, use alternative implementations or need to maintain ancient code.
 * The definition we use is the same as referenced in the Wikipeia article STL that I believe was linked to in the text Standard Template Library. I will try to look into what is stated but I remember putting a clear effort into making it understandable to readers. --Panic (discuss • contribs) 01:40, 7 March 2013 (UTC)