<p><pre><code>    you see code with tons of indirect function calls, 
    lots of wrapper functions (ie one function massages 
    some arguments a bit and then just calls another 
    function), and no, it&#x27;s not inlined because it&#x27;s of
    ten all about interfacing between different library
    levels (webkit, various font rendering libraries, low-
    level drivers for &quot;in memory&quot; vs &quot;on screen&quot; yadda
    yadda)
</code></pre>
can anyone speak to these criticisms?<p>i often write code that starts as this:<p><pre><code>    function ae(arr) {
      &#x2F;&#x2F;do 
      &#x2F;&#x2F;first 
      &#x2F;&#x2F;something to arr
      &#x2F;&#x2F;do
      &#x2F;&#x2F; second
      &#x2F;&#x2F;  something to arr
      &#x2F;&#x2F;do
      &#x2F;&#x2F; third
      &#x2F;&#x2F;  something to arr
    return arr
    }
</code></pre>
then refactor it as:<p><pre><code>    function first(arr) {
      &#x2F;&#x2F; do
      &#x2F;&#x2F;  something 
      return arr }
    function sec(arr) {
      &#x2F;&#x2F; do
      &#x2F;&#x2F;  something 
      return arr }
    function third(arr) {
      &#x2F;&#x2F; do
      &#x2F;&#x2F;  something 
      return arr }

    function ae(arr) {
      arr=first(arr)
      arr=second(arr)
      arr=third(arr)
    return arr
    }
</code></pre>
is this what torvalds is referring to?<p>i thought i had done &#x27;extensive&#x27; research on the perf burden of function calls and found them to be negligible so i decided to refactor for the sake of readability<p>what&#x27;s best practices in regard to indirect function calls, wrapper functions, and inlining?