Re: Concerns over handling of bug #49105
| From: | Alexander Trauzzi | Date: | Fri, 31 Jul 2009 13:32:18 +0000 |
| Subject: | Re: Concerns over handling of bug #49105 | ||
| References: | 1 2 3 4 5 6 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-65269@lists.php.net to get a copy of this message | ||
Hannes,
> Can you imagine what would happen if every single bogus bug got the
> same treatment as this one?
I can as a matter of fact...Nothing would change. Because most requests for
improvements or changes are systematically discarded.
>This is how PHP works and it will not change.
>If you want additional features then request and write access to the
>/rfc/ namespace on the wiki and write an RFC.
>If you want to increase the chances of that feature making it in
>a) attach a patch
>b) find a dev thats interested in the RFC and bribe him to create a patch
I do not have the skills to implement such a feature, so it would be
pointless to try and guilt me into making it, that's a bit of an impasse! :)
However if you're being sincere, that's a good suggestion! Do you think it
is worthwhile? I was thinking about putting up my second idea which is to
create a new modifier (akin to static, protected, public, abstract...)
which would allow for properties to be flagged for copy into a subclass.
This would make the improvement (as we've determined that a "change" is out
of the question) less obtrusive and purely optional.
Do you or anyone else have thoughts on this? Maybe you could help me get it
put up there and submit input as to how it might be accomplished?
- Alex