A lot of times, it will tell you what kind of error it is....if it's a
parse error, the first thing to look for is a missing semi-colon or
something. Other than that, braces and parens are the ones that I miss
the most. It's just a limitation of the PHP debugger right now. It might
be fixed in later versions, but until then I'd just suggest an editor
that does syntax highlighting. It's helped me not miss as many little
things like that.
-enygma
"Coughlan, Andy-HQ" wrote:
>
>
> Hi Guys and Gals,
>
> Whilst developing various php pages I noticed that occasionally when I
> get an error in a page the parser won't tell me which line the error
> is on, and just shows "error on line 1" even if the error is on line
> 93. It isn't every page that does it, although I've tried saving an
> offending file as a different name and this symptoms still occur. Has
> anyone else had a similar experience, and, if so, do they know if
> there's a fix for it?
>
> Andy
>
> Andy Coughlan
> Marketing Communications Assistant
> [EMAIL PROTECTED]
>
> Smiths Group plc Registered in England under No:137013
> Registered office: 765 Finchley Road, London NW11 8DS, UK
>
> This E-mail and any files transmitted with it are confidential and
> intended
> solely for the use of the individual or entity to whom they are
> addressed.
> This E-mail does not constitute a commitment by Smiths Group plc or
> any of its subsidiary companies
--
[EMAIL PROTECTED]
----------------------------------
PHPDeveloper.org - News, tuorials and forums all for you
http://www.phpdeveloper.org
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
