ID: 42115 Updated by: [EMAIL PROTECTED] Reported By: mattsch at gmail dot com Status: Open Bug Type: Documentation problem Operating System: Gentoo Linux PHP Version: 5.2.3 New Comment:
Code: http://pastie.caboo.se/82738 Output: http://pastie.caboo.se/82739 It seems that the static can really go either side of the visibility keyword for all visibilities. I can confirm that this is the case since V5.0.0 (just downloaded that from (3 years old this month). Previous Comments: ------------------------------------------------------------------------ [2007-07-27 07:12:46] [EMAIL PROTECTED] Documentation problem it is ------------------------------------------------------------------------ [2007-07-27 03:33:29] mattsch at gmail dot com I don't argue that php is a loosely typed language but it does have rules and it should either adhere by them or change the rules. Currently the documentation says that static must come after visibility: http://www.php.net/manual/en/language.oop5.static.php "The static declaration must be after the visibility declaration." So either emit an E_STRICT warning or change the documentation to include this syntax as well. ------------------------------------------------------------------------ [2007-07-27 02:27:14] judas dot iscariote at gmail dot com No, PHP is a dynamic language, I dont see why this should raise any kind of error 1. does not cause any problem. 2.it is perfectly valid code. ------------------------------------------------------------------------ [2007-07-26 20:14:20] mattsch at gmail dot com Description: ------------ Contrary to the documentation, you're allowed to put the static keyword before the visibility keyword. Shouldn't this throw an E_STRICT warning? Reproduce code: --------------- <? class foo { static public function bar($foo){ echo $foo; } } foo::bar('test'); ?> Expected result: ---------------- E_STRICT: You cannot declare static before a visibility keyword. Actual result: -------------- Echoes "test" without warning. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=42115&edit=1
