|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Return to Bug #60536
Patch property008.phpt revision 2011-12-16 16:46 UTC by
Patch property007.phpt revision 2011-12-16 16:19 UTC by
Patch property006.phpt revision 2011-12-16 16:19 UTC by
Patch property005.phpt revision 2011-12-16 16:19 UTC by
Patch bug60536.phpt revision 2011-12-16 15:57 UTC by
Patch bug60536.patch revision 2011-12-16 15:54 UTC by

Patch property006.phpt for Scripting Engine problem Bug #60536

Patch version 2011-12-16 16:19 UTC

Return to Bug #60536 | Download this patch
Patch Revisions:


Introducing new private variables of the same name in a subclass is ok, and does not lead to any output. That is consitent with normal inheritance handling.
error_reporting(E_ALL | E_STRICT);

class Base {
  private $hello;    

trait THello1 {
  private $hello;

// Now we use the trait, which happens to introduce another private variable
// but they are distinct, and not related to each other, so no warning.
class SameNameInSubClassNoNotice extends Base {
    use THello1;

// now the same with a class that defines the property itself,
// that should give the expected strict warning.

class Notice extends Base {
    use THello1;
    private $hello;

Strict Standards: Notice and THello1 define the same property ($hello) in the composition of Notice. This might be incompatible, to improve maintainability consider using accessor methods in traits instead. Class was composed in %s on line %d
PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Wed Oct 28 23:01:24 2020 UTC