Concerns over handling of bug #49105
| From: | Alexander Trauzzi | Date: | Thu, 30 Jul 2009 17:25:05 +0000 |
| Subject: | Concerns over handling of bug #49105 | ||
| Groups: | php.qa | ||
| Request: | Send a blank email to php-qa+get-65263@lists.php.net to get a copy of this message | ||
Hello to the list!
I just wanted to express some concerns over the handling of bug #49105 over
here: http://bugs.php.net/bug.php?id=49105
It seemed to be overnight that the bug was marked as "bogus" without much
due process or consideration. The speed at which the issue was discarded is
somewhat alarming. Also, a contributor who attempted to validate the
current behaviour in PHP readily proved my concern by inadvertently
producing defective code.
I've been doing some additional research today, which I hope supports my
issue:
Here is a possible similar issue which received exactly the same treatment:
http://bugs.php.net/bug.php?id=44315
Here is an issue (pre-late-static-binding) which relies on parent:: for
accessing the parent class property:
http://bugs.php.net/bug.php?id=30451&edit=1
Strictly in terms of the PHP QA process, marking a bug as bogus does have a
procedure outlined: http://qa.php.net/handling-bugs.php where it says:
"Be
100% it's really bogus and also be sure it's not a documentation bug."
I do not feel as though this has been done and I hope that an equal amount
of effort could be made to at least help me understand why the issue is not
even going to be considered. I have done lots of research into the
behaviour as well as the habits of PHP bug maintainers. Being directed to a
manual that makes no mention of the issue seems somewhat dismissive.
If we apply some careful thought here, it's clear that subclasses should be
making copies of all properties from their parent and when a parent wishes
to refer to the subclass property, it uses static:: (which is why we have
late static binding) and when a child wishes to refer to the parent
property, it uses parent:: (which is why it exists in the first place).
To use a corny analogy: If I write a static bicycle class, why would my
static motorcycle class that extends it suddenly lose a wheel??
I apologize for my persistence, however I do want to make sure this hasn't
been overlooked. OO functionality in PHP has been flourishing over the past
while. Features like late static binding have also received similar
treatment in the past: http://bugs.php.net/bug.php?id=30934
....and so I'm hoping this isn't another case of a landmark improvement being
overlooked.
- Alex