Effective STL: 50 Specific Ways to Improve Your Use of the Standard Template Library (Paperback)
立即出貨 (庫存 < 3)
貴賓價: $1,724Effective C++: 55 Specific Ways to Improve Your Programs and Designs, 3/e (Paperback)
貴賓價: $1,663More Effective C++: 35 New Ways to Improve Your Programs and Designs (Paperback)
貴賓價: $2,076Refactoring: Improving the Design of Existing Code (Hardcover)
貴賓價: $1,995Design Patterns: Elements of Reusable Object-Oriented Software (Hardcover)
貴賓價: $2,343Data Mining: Concepts and Techniques
貴賓價: $1,829Code Complete: A Practical Handbook of Software Construction, 2/e (Paperback)
貴賓價: $1,637More Exceptional C++ (Paperback)
貴賓價: $2,151Modern C++ Design: Generic Programming and Design Patterns Applied (Paperback)
貴賓價: $1,235Computer Architecture: A Quantitative Approach, 3/e(精裝本)
C++'s Standard Template Library is revolutionary, but learning to use it well has always been a challenge for students. In Effective STL, best-selling author Scott Meyers (Effective C++, More Effective C++) reveals the critical rules of thumb employed by the experts -- the things they almost always do or almost always avoid doing -- to get the most out of the library. This book offers clear, concise, and concrete guidelines to C++ programmers. While other books describe what's in the STL, Effective STL shows the student how to use it. Each of the book's 50 guidelines is backed by Meyers' legendary analysis and incisive examples, so the student will learn not only what to do, but also when to do it - and why.
Item 2: Beware the illusion of container-independent code.
Item 3: Make copying cheap and correct for objects in containers.
Item 4: Call empty instead of checking size against zero.
Item 5: Prefer range member functions to their single-element counterparts.
Item 6: Be alert for C++'s most vexing parse.
Item 7: When using containers of newed pointers, remember to delete the pointers before the container is destroyed.
Item 8: Never create containers of auto_ptrs.
Item 9: Choose carefully among erasing options.
Item 10: Be aware of allocator conventions and restrictions.
Item 11: Understand the legitimate uses of custom allocators.
Item 12: Have realistic expectations about the thread safety of STL containers.
2. Vector and string.
Item 14: Use reserve to avoid unnecessary reallocations.
Item 15: Be aware of variations in string implementations.
Item 16: Know how to pass vector and string data to legacy APIs.
Item 17: Use "the swap trick" to trim excess capacity.
Item 18: Avoid using vector
3. Associative Containers.
Item 20: Specify comparison types for associative containers of pointers.
Item 21: Always have comparison functions return false for equal values.
Item 22: Avoid in-place key modification in set and multiset.
Item 23: Consider replacing associative containers with sorted vectors.
Item 24: Prefer map::insert to map::operator when efficiency is a concern.
Item 25: Familiarize yourself with the nonstandard hashed containers.
Item 27: Use distance and advance to convert const_iterators to iterators.
Item 28: Understand how to use a reverse_iterator's base iterator.
Item 29: Consider istreambuf_iterators for character by character input.
Item 31: Know your sorting options.
Item 32: Follow remove-like algorithms by erase if you really want to remove something.
Item 33: Be wary of remove-like algorithms on containers of pointers.
Item 34: Note which algorithms expect sorted ranges.
Item 35: Implement simple case-insensitive string comparisons via mismatch or lexicographical_compare.
Item 36: Use not1 and remove_copy_if to perform a copy_if.
Item 37: Use accumulate or for_each to summarize sequences.
6. Functors, Functor Classes, Functions, etc.
Item 39: Make predicates pure functions.
Item 40: Make functor classes adaptable.
Item 41: Understand the reasons for ptr_fun, mem_fun, and mem_fun_ref.
Item 42: Make sure less
7. Programming with the STL.
Item 44: Prefer member functions to algorithms with the same names.
Item 45: Distinguish among count, find, binary_search, lower_bound, upper_bound, and equal_range.
Item 46: Consider function objects instead of functions as algorithm parameters.
Item 47: Avoid producing write-only code.
Item 48: Always #include the proper headers.
Item 49: Learn to decipher STL-related compiler diagnostics.
Item 50: Familiarize yourself with STL-related web sites.
Appendix A. Locales and Case-Insensitive String Comparisons.
Appendix B. Remarks on Microsoft's STL Platforms.