Has anyone already solved the not-enough-information problem when
using the -l (lint) switch to check syntax?
I make heavy use of include(), so when php complains about some syntax
problem, the line number it reports is never even close to correct.
And since even the lint switch doesn't cause the alleged offending
line to be written out, there's no good way to start backtracking.
Is there some switch I'm missing, or is there a version of php.exe
already hacked to display the problematic line? If there's not, then
I'll do the hack, but I would *much* prefer not to have to.
Thanks,
Margaret
--
(To mail me, please change .not.invalid to .net, first.
Apologies for the inconvenience.)
using the -l (lint) switch to check syntax?
I make heavy use of include(), so when php complains about some syntax
problem, the line number it reports is never even close to correct.
And since even the lint switch doesn't cause the alleged offending
line to be written out, there's no good way to start backtracking.
Is there some switch I'm missing, or is there a version of php.exe
already hacked to display the problematic line? If there's not, then
I'll do the hack, but I would *much* prefer not to have to.
Thanks,
Margaret
--
(To mail me, please change .not.invalid to .net, first.
Apologies for the inconvenience.)