Why doesn't lint tell me the line number and nature of the parse error?

Viewed 9885

I'm calling php lint from a Windows batch file, like so:

@echo off
for %%f in (*.php) do php -l %%f

When a file contains a syntax error, it only outputs Errors parsing xxx.php. 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?

3 Answers
Related