title: Defining OnClickListener separately or inside setOnClickListener()?
body: <p>I was filling inside a <code>getView()</code> of an adapter while defining the click listeners, this got me wondering:</p>
  
  <p><strong>Performance-wise</strong>, is there a difference between these two implementations:</p>
  
  <p><em>Defining onClickListener separately:</em></p>
  
  <pre><code>View.OnClickListener mClickListener = new View.OnClickListener() {
      @Override
      public void onClick(View view) { //... }
  };
  mView.setOnClickListener(mClickListener);
  </code></pre>
  
  <p>and</p>
  
  <p><em>Defining onClickListener as the argument:</em></p>
  
  <pre><code>mView.setOnClickListener(new View.OnClickListener() {
      @Override
      public void onClick(View view) { //... }
  });
  </code></pre>
  
  <hr>
  
  <p>As <code>getView()</code> is frequently called, my though is that even small differences in its implementation would have big effect in app's performance. But I'm not sure. </p>
  
  <p>So, which of the above is recommended regarding the performance/memory? Or aren't they that different to matter?</p>