On Thursday 16 June 2005 11:27, Sebastian Mendel wrote: > > I guess, this will more likely produce an error message like this: > > > > Parse error: syntax error, unexpected T_PUBLIC, expecting T_STRING in > > public.php on line 2
right > > So I'm strongly against this change. If you want to run PHP4 code in > > PHP5, disable E_STRICT. +1 > id dont know, but isnt there a difference between where the keywords are > placed? No, it's a parser keyword and a keyword can't be used as a function name. > and if it is so, then this would also be a candidate for > > "NOTICE: 'public' is a keyword in PHP 5" in php 4.4 No. No "errors" for "forward compatibility". johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
