Re: Class Properties in Interfaces?
| From: | Stanislav Malyshev | Date: | Mon, 19 May 2008 16:25:47 +0000 |
| Subject: | Re: Class Properties in Interfaces? | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-37723@lists.php.net to get a copy of this message | ||
Hi!
Would the following be acceptable? (Not E_STRICT) If error_reporting does not include E_STRICT, thenI think making the language internals depend on error_reporting setting is not a very good idea, especially on E_STRICT. I.e., I have nothing against making unset() trigger E_STRICT if it is warranted, though I'm not sure how exactly you'd implement that. But changing what unset() does to symbol table depending on E_STRICT is IMHO wrong. Error reporting is for reporting errors to the user, not switching engine to different incompatible behavior. Imagine WTF factor if same method call would act differently with and without @.
interface foo { public bar read fReadBar, write fWriteBar; }You really don't want to make read and write keywords ;) -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com