blob: d5e4ddc617e4abd6a42ce740a5a761264d41fc33 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
--TEST--
Potentially conflicting properties should result in a strict notice. Property use is discorage for traits that are supposed to enable maintainable code reuse. Accessor methods are the language supported idiom for this.
--FILE--
<?php
error_reporting(E_ALL);
trait THello1 {
private $foo;
}
trait THello2 {
private $foo;
}
echo "PRE-CLASS-GUARD-TraitsTest\n";
error_reporting(E_ALL & ~E_STRICT); // ensuring that it is only for E_STRICT
class TraitsTest {
use THello1;
use THello2;
}
error_reporting(E_ALL | E_STRICT);
echo "PRE-CLASS-GUARD-TraitsTest2\n";
class TraitsTest2 {
use THello1;
use THello2;
}
var_dump(property_exists('TraitsTest', 'foo'));
var_dump(property_exists('TraitsTest2', 'foo'));
?>
--EXPECTF--
PRE-CLASS-GUARD-TraitsTest
PRE-CLASS-GUARD-TraitsTest2
Strict Standards: THello1 and THello2 define the same property ($foo) in the composition of TraitsTest2. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in %s on line %d
bool(true)
bool(true)
|
