Re: (*PATCH*) getters/setters Implementation
| From: | Christopher Jones | Date: | Thu, 29 Mar 2012 18:13:31 +0000 |
| Subject: | Re: (*PATCH*) getters/setters Implementation | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-59206@lists.php.net to get a copy of this message | ||
On 03/28/2012 08:13 PM, Clint M Priest wrote:
What are the next steps to get this added to some future release? Attached is a patch against ~/trunkA couple of brief comments from the sidelines without having followed previous discussion in detail: - The RFC appears to have open questions e.g about the need for readonly etc keywords - The tests and RFC are out of sync regarding naming, e.g. readonly vs read-only - The RFC makes no mention of backward compatibility issues - Did I miss seeing tests that pass in unexpected values to the methods? - I would expect a larger number of tests overall when the feature is merged/completed. - If these are indeed magic methods they need "__" prefixes, so consider the names __getter and __setter - I'd suggest biting the github bullet and creating your own PHP fork with your patches. People will be able to test and you might get more feedback. -- Email: christopher.jones@oracle.com Tel: +1 650 506 8630 Blog: http://blogs.oracle.com/opal/