Re: debuging and getting mor information about failures

These errors are usually caused by an extra or missing brace or quote/apostrophe/backtick. The best way to find where this is happening is to use another error. Start at the bottom of your script and introduce some garbage on a line by itself. "asdf" for example. This should cause a parse error when encountered. Move this up a few lines at a time, until the original parse error goes away, and this one starts. This will help you identify where your problem is. This is a very frustrating error message, but the above should take some of the pain away. :-) HTH. Pete. -- -- Peter James petej@phparch.com php|architect The Magazine for PHP Professionals http://www.phparch.com "chrstian brensteiner" <eingfoan@yahoo.de> wrote in message news:20030729071131.17365.qmail@pb1.pair.com... > whats the best option to get more information about a failure in your sorce > code ? > > whenever i get failures that are situated at the very end of my script how > do i get to know wherer they start? > > now i have get from apache + php this return > > Parse error: parse error, unexpected $ in > c:\programme\easyphp\www\cms\procede_presse.php on line 268 > > 268 is the last line of my script how to deal with those failures in an > intelligent way? > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php >