title: Why doesn't lint tell me the line number and nature of the parse error?
body: <p>I'm calling php lint from a Windows batch file, like so:</p>
  
  <pre><code>@echo off
  for %%f in (*.php) do php -l %%f
  </code></pre>
  
  <p>When a file contains a syntax error, it only outputs <code>Errors parsing xxx.php</code>. Is there any way to get it to tell me what the nature of the error is, and what line it's on? Maybe another switch?</p>