category网志分类
- 未分类
- a box of chocolate
- life in IT industry
- MySQL Replication
- programming & research
programming & research
- setting process affinity in windows in command line
- simple command line timer for windows
- starting / stopping service in windows using command line
- simple implementation of all to all communication using send/recv
- get thread id in pthread
- three ways of saying "count lines of code of my project"
- CUDA programming pitfalls 1: atomic operations
- 在C程序中调用C++代码
- Effective STL 3: Make copying cheap and correct for objects in containers
- Effective STL 1: Choose your containers with care
- More Effective C++ 28: Smart pointers
- More Effecitve C++ 27: Requiring or prohibiting heap-base objects
- More Effective C++ 26: Limiting the number of objects of a class
- More Effective C++ 25: Virtualize constructors and non-member functions
- More Effective C++ 24: Understand the costs of virtual functions, multiple inheritance...
- More Effective C++ 23: Consider alternative libraries
- More Effective C++ 22: Consider using op= instead of stand-alone op
- You Raise Me Up
- More Effective C++ 21: Overload to avoid implicit type conversions
- More Effective C++ 20: Facilitate the return value optimization
- More Effecitve C++ 19: Understand origin of temporary objects
- More Effecitve C++ 18: Amortize the cost of expected computation
- More Effective C++ 17: Consider using lazy evaluation
- 又见下沙
- More Effective C++ 16: Remember the 80-20 rule
- More Effective C++ 15: Understand the costs of exception handling
- More Effective C++ 14: Use exception specifications judiciously
- More Effective C++ 13: Catch exceptions by reference
- More Effective C++ 12: Understand how throwing an exception differs from passing a parameter or ...
- More Effective C++ 11: Prevent exceptions from leaving destructors
- Effective C++ 10: Prevent resource leaks in constructors
- More Effective C++ 9: Use destructors to prevent resource leaks
- More Effective C++ 8: Understand different meanings of new and delete
- More Effective C++ 7: Never overload && || or ,
- More Effecitve C++ 6: Distinguish between postfix and prefix forms of increment and decrement
- More Effective C++ 5: Be wary of user-defined conversion funcitons
- More Effective C++ 4: Avoid gratuitous default constructors
- More Effective C++ 3: Never treat arrays polymorphically
- More Effective C++ 2: Prefer C++-style casts
- More Effective C++ 1: Distinguish between pointers and references
- Effecitve C++ 50: Improve your understanding of C++
- Effective C++ 49: Familiarize yourself with the standard library
- Effective C++ 48: Pay attention to compiler warnings
- Effective C++ 47: Ensure that non-local static objects are initialized before they are used
- Effective C++ 46: Prefer compile-time and link-time errors to runtime errors
- Effective C++ 45: Know what C++ silently writes and calls
- Effective C++ 44: Say what you mean; understand what you're saying
- Effective C++ 43: Use multiple inheritance judiciously
- Effective C++ 42: Use private inheritance judiciously
- Effective C++ 41: Differentiate between templates and inheritance
- Effective C++ 40: Model "has-a" or "is-implemented-in-terms-of" through layering
- Effective C++ 39: Avoid casts down the inheritence hierarchy
- Effective C++ 38: Never redefine an inherited default parameter value
- Effective C++ 37: Never redefine an inherited nonvirtual function
- Effective C++ 36: Differentiate between inheritance of interface and inheritance of implementation
- Effective C++35: Make sure public inheritance models "isa"
- 如何设置cout的输出格式
- Effective C++ 33: Use inlining judiciously
- Effective C++ 32: Postpone variable definitions as long as possible
- VC++: internal heap limit reached...
- Effective C++ 30. Avoid member functions that return non-const references or pointers less accessibl
- 突然感觉到自己的无知
- Effective C++ Note 29: Avoid returning "handles" to internal data
- Effective C++ Note 28: Use of namespace
- Effective C++ Note 27: Explicitly disallow use of implicitly generated member functions...
- Effective C++ Note 26: Guard against potential ambiguity
- Effective C++ Note 25: Avoid overloading on a pointer and a numberical type
- Effective Note 24: function overloading vs parameter defaulting
- Effective C++ Note 23: Don't try to return a reference when you must return an object
- Effective C++ Note 22: Prefer pass-by-reference to pass-by-value
- Effective C++ Note 21: Use const whenever possible
- Effective C++ Note 20: Avoid data members in the public interface
- Effective C++ Note 19: member functions, non-member functions and friend functions
- Effecitve C++ Note 18: Strive for class interfaces that are complete and minimal
- Effective C++ Note 17: Check for assignment to self in operator=
- Effective C++ Note 16: assign to all data members in operator =
- Effective C++笔记１５： 让 operator = 返回一个指向 *this 的引用
- Effective C++ 笔记１４： 将基类的析构函数声明为虚函数
- Effective C++ 笔记１３： 成员变量的初始化顺序
- Effective C++ 笔记１２： 在 constructors 中对成员变量采取初始化而不要使用赋值
- Effective C++ 笔记１１： 为有指针成员的类重载 copy constructor 跟 operator =
- Effective C++ 笔记１０： 在重载操作符 new 的同时重载 delete
- Effective C++ 笔记９： 重载操作符 new 时不要把“正常”的 new 格式给覆盖掉
- Effective C++ 笔记８： 重载 new 和 delete 时要遵从的惯例
- Effective C++ 笔记７： 对内存不足的处理
- Effective C++ 笔记６： 记得在析构函数中把指针类型的成员变量 delete 掉
- Effective C++ 笔记５： 使用相同形式的 new 和 delete
- Effective C++ 笔记４： 用 // 代替 /* */ 做注释
- Effective C++ 笔记３： 用 new和delete 代替 malloc和free
- Effective C++ 笔记２： 用<iostream>代替<stdio.h>
- Effective C++ 笔记１： 用const和inline代替define