Bug #66926 [Opn->Fbk]: Missing Information in translation

Edit report at https://bugs.php.net/bug.php?id=66926&edit=1 ID: 66926 Updated by: cmb@php.net Reported by: wako057 at gmail dot com Summary: Missing Information in translation -Status: Open +Status: Feedback Type: Bug Package: Documentation problem Operating System: Debian PHP Version: Irrelevant -Assigned To: +Assigned To: cmb Block user comment: N Private report: N New Comment: The reported behavior is to be expected, see the man page on "Constructors and Destructors"[1]. You have filed this as "Missing Information in translation", so we have to assume that there is a documentation translation problem. It is not clear, however, which translation (i.e. language) is affected. Can you please clarify? [1] <http://php.net/manual/en/language.oop5.decon.php> Previous Comments: ------------------------------------------------------------------------ [2014-03-18 16:39:53] wako057 at gmail dot com Description: ------------ I've tested this issue on php 5.3.28 and php 5.5.10 When the parser found in class a method called as the class, insensitive to the case, it generate a Strict Standard error. But if it found the __construct first, at this moment no error is raised. With namespace the case doesn't happened at all. Test script: --------------- <?php class Foo { public function foo() { echo 'ahaha'; } function __construct() { echo 'hihi'; } } Generate a: PHP Strict Standards: Redefining already defined constructor for class Foo BUT <?php class Foo { function __construct() { echo 'hihi'; } public function foo() { echo 'ahaha'; } } Don't <?php namespace Bar; class Foo { public function foo() { echo 'ahaha'; } function __construct() { echo 'hihi'; } } new Foo(); Neither Expected result: ---------------- When a __construct is present, no error should be raised Actual result: -------------- Strict Standards: Redefining already defined constructor for class Foo in /var/www/tt.php on line 7 ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=66926&edit=1