Re: Seeking 'coalesce' php internal function
| From: | Jared White | Date: | Fri, 05 May 2006 01:18:16 +0000 |
| Subject: | Re: Seeking 'coalesce' php internal function | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-23157@lists.php.net to get a copy of this message | ||
On May 4, 2006, at 2:06 PM, Pierre wrote:
On Thu, 04 May 2006 14:27:09 -0500 dante@vocalspace.com ("D. Dante Lorenso") wrote:Well, from where I'm setting, Dante has brought up excellent points that were never covered before according to my look at the list archives. In fact, I find this situation indicative of a larger problem, which is that extremely important discussions of major issues with the language get breezed by far too quickly just because someone decides it's not interesting enough or it's time to move on (*cough* named parameters *cough*). I think the concept behind filled() is sound, has merit, and is worth talking about seriously. JaredDetracting from my goal of having 'filled()' included in core, I'd have to say that as I see input filtering defined, that could be entirely written as part of Zend Framework in PHP and doesn't need to exist as part of the language core. filled(), OTOH, must be written in 'zend' core because it simply can not be written as an extension or in userspace without triggering errors (undefined variables) or creating unwanted variables (pass by reference).I think it is time for you to do two things. The first is to read this list archive about ifsetor (and other names it has), it will spare you some ink and us some bandwidth. The second is to actually try the filter extension and get some knowledge about what can be done where and why. There is eventually a third one, try to imagine than the Z Framework has nothing to do with php.net. It is not an attack, but it seems you are putting so much effort on this topic without actually having read what has been said and decided.