Changes between Version 4 and Version 5 of CodeAndMemoryPerformance

Timestamp:

May 12, 2013, 9:43:25 AM (11 years ago)

Author:

tuan kuranes

Comment:

--

CodeAndMemoryPerformance

@@ -18 +18 @@
  * Do whatever possible to avoid any allocation/free during the frame loop. 
 
-First simplest step,  we can agree on avoiding all "hidden" temporary object allocation by following simple rules, which are explained [http://www.tantalon.com/pete/cppopt/main.htm here], and as a recap:
+First simplest step, avoiding all "hidden" temporary object allocation by following simple rules, which are explained [http://www.tantalon.com/pete/cppopt/main.htm here], and as a recap:
 
  * Pass Class Parameters by Reference
@@ -26 +26 @@
  * Use Operator= Instead of Operator Alone
  * Use Explicit Constructors
-
-I'll add:
-
  * Prefer passing parameter by value whenever possible ( don't return object allocated on the stack, don't ever return containers allocated on the stack). [[BR]]( you could be sure that all compilers does trigger any form  of return value optimization ( RVO, NRVO, URVO, opy elision), by  checking assembly code generated, but that doesn't change that debug  builds will be slower because of not doing the optimization anyway, and  impose the burden of checking it if new/old compiler/transpiler is added  to compilation supports.)