title: JSHint not recognizing "intended scopes" for variables
body: <p>Based on the description of the <code>funcscope</code> option in its <a href="http://www.jshint.com/docs/" rel="nofollow">documentation</a>, it seems JSHint recognizes the utility of the variables being declared in "intended scopes" e.g. control structures etc. (even though in reality within a function in JS there is only one scope).</p>
  
  <p>Why, then, does it throw up an error for the following, saying that <code>i</code> is declared multiple times?</p>
  
  <pre><code>if (condition) {
      var i = 1;
      //
  }
  else {
      var i = 2;
      //
  }
  </code></pre>
  
  <p>Setting <code>funcscope</code> to either true or false does not help. Is there any way to suppress this error?</p>
  
  <p>(I like having "logical/intended" variable scopes, and "defining" variables as close to where they are required. Helps me when code chunks need to be moved around.</p>
  
  <p>EDIT:
  I know about variable hoisting. But I don't subscribe to Douglas Crockford's views on declaring all <code>var</code>s at the top of the function. That makes code harder to read, as well as harder to refactor when you have to move code snippets around. 
  If you read the documentation of <code>funcscope</code> at the JSHint homepage, it also talks about <em>intended scope</em>, which is exactly what I am referring to as well. I am asking my question in this context)</p>