Bug #55554 [Opn->Csd]: Trait methods overriding legacy constructors

From: Date: Sun, 17 Nov 2013 09:36:05 +0000
Subject: Bug #55554 [Opn->Csd]: Trait methods overriding legacy constructors
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-182797@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=55554&edit=1 ID: 55554 Updated by: laruence@php.net Reported by: ryan at zuttonet dot com Summary: Trait methods overriding legacy constructors -Status: Open +Status: Closed Type: Bug Package: Scripting Engine problem Operating System: Ubuntu PHP Version: 5.4.0alpha3 Block user comment: N Private report: N New Comment: Automatic comment on behalf of gron Revision: http://git.php.net/?p=php-src.git;a=commit;h=7e4b9800f48dc43e4d65afb70fcca171a7ac0def Log: Fixed Bug #55554 (Legacy constructors not handled properly) [TRAITS] [DOC] # The handling of legacy constructors defined by traits was corrected. # They are now properly registered and used on instantiation. # The situation for conflicting legacy and __construct constructors is # mostly identical. If they are defined in the class, they override conflicts # and do not collide. However, in case different styles are mixed, between # class and trait definition, we assume a programmer's mistake and report # a collision. # # BTW: +1 for all the fixed tests! make test is fun again. Previous Comments: ------------------------------------------------------------------------ [2013-04-01 16:05:43] holdthatprospect at hotmail dot com Try this info: Grands____------Regularly--- ______Grand!!!!!!!Bills365/7Bills!!!!!!!bills!!!!!! ------------------------------------------------------------------------ [2012-07-24 23:39:33] rasmus@php.net Automatic comment on behalf of gron Revision: http://git.php.net/?p=php-src.git;a=commit;h=7e4b9800f48dc43e4d65afb70fcca171a7ac0def Log: Fixed Bug #55554 (Legacy constructors not handled properly) [TRAITS] [DOC] # The handling of legacy constructors defined by traits was corrected. # They are now properly registered and used on instantiation. # The situation for conflicting legacy and __construct constructors is # mostly identical. If they are defined in the class, they override conflicts # and do not collide. However, in case different styles are mixed, between # class and trait definition, we assume a programmer's mistake and report # a collision. # # BTW: +1 for all the fixed tests! make test is fun again. ------------------------------------------------------------------------ [2012-04-18 09:48:27] laruence@php.net Automatic comment on behalf of gron Revision: http://git.php.net/?p=php-src.git;a=commit;h=7e4b9800f48dc43e4d65afb70fcca171a7ac0def Log: Fixed Bug #55554 (Legacy constructors not handled properly) [TRAITS] [DOC] # The handling of legacy constructors defined by traits was corrected. # They are now properly registered and used on instantiation. # The situation for conflicting legacy and __construct constructors is # mostly identical. If they are defined in the class, they override conflicts # and do not collide. However, in case different styles are mixed, between # class and trait definition, we assume a programmer's mistake and report # a collision. # # BTW: +1 for all the fixed tests! make test is fun again. ------------------------------------------------------------------------ [2011-10-16 18:45:37] gron@php.net This bug has been fixed in SVN. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. ------------------------------------------------------------------------ [2011-10-09 11:18:06] gron@php.net This bug has been fixed in SVN. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=55554 -- Edit this bug report at https://bugs.php.net/bug.php?id=55554&edit=1

« previous php.bugs (#182797) next »