This is obvious syntax error that should stop execution. There are other warnings that continue with warning message with obvious syntax error. (such as malformed break statement)
IMO, language should raise fatal error for syntax errors instead of warning and let programmer fix errors for these kind of errors. Or do we have policy that make execution continue much as possible? It's fair policy for scripting language, but this policy makes difficult to write robust scripts especially for newbies. We may want to change the behavior for ZE2. Let's make clear where we're heading. -- Yasuo Ohgaki PHP Bug Database wrote: > ATTENTION! Do NOT reply to this email! > To reply, use the web interface found at > http://bugs.php.net/?id=14491&edit=2 > > > ID: 14491 > Updated by: [EMAIL PROTECTED] > Reported By: [EMAIL PROTECTED] > -Status: Analyzed > +Status: Closed > Bug Type: Scripting Engine problem > Operating System: Linux > PHP Version: 4.1.0 > New Comment: > > It's fine as it is > > > Previous Comments: > ------------------------------------------------------------------------ > > [2001-12-14 12:53:18] [EMAIL PROTECTED] > > Bad english correction ;) > Shoud this be an error? instead of warning? > > Status = Analyzed > > ------------------------------------------------------------------------ > > [2001-12-13 14:12:56] [EMAIL PROTECTED] > > Is't this should be an error? instead of warning? > > <?php > \ echo "aa"; > ?> > > gives > > Warning: Unexpected character in input: '\' (ASCII=92) state=1 in > /home/yohgaki/public_html/bugs/test.php on line 2 > aa > > > > ------------------------------------------------------------------------ > > > > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
