mirror of
https://github.com/php/php-src.git
synced 2024-09-24 11:27:28 +00:00
e14354af21
# 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.
47 lines
986 B
PHP
47 lines
986 B
PHP
--TEST--
|
|
Bug #55137 (Legacy constructor not registered for class)
|
|
--FILE--
|
|
<?php
|
|
|
|
// Test that the behavior is consistent with the existing handling of new
|
|
// and legacy constructors.
|
|
// Here, the traits conflicts are overridden by local definitions,
|
|
// and the two constructor definitions do not directly collide in that case.
|
|
|
|
trait TC1 {
|
|
public function __construct() {
|
|
echo "TC1 executed\n";
|
|
}
|
|
public function ReportCollision() {
|
|
echo "TC1 executed\n";
|
|
}
|
|
}
|
|
|
|
trait TC2 {
|
|
public function __construct() {
|
|
echo "TC2 executed\n";
|
|
}
|
|
public function ReportCollision() {
|
|
echo "TC1 executed\n";
|
|
}
|
|
}
|
|
|
|
class ReportCollision {
|
|
use TC1, TC2;
|
|
|
|
public function __construct() {
|
|
echo "New constructor executed\n";
|
|
}
|
|
public function ReportCollision() {
|
|
echo "Legacy constructor executed\n";
|
|
}
|
|
}
|
|
|
|
|
|
echo "ReportCollision: ";
|
|
$o = new ReportCollision;
|
|
|
|
|
|
--EXPECTF--
|
|
ReportCollision: New constructor executed
|