Re: Internals read-only
| From: | Richard Quadling | Date: | Thu, 13 Dec 2007 15:54:47 +0000 |
| Subject: | Re: Internals read-only | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-34014@lists.php.net to get a copy of this message | ||
On 13/12/2007, Jani Taskinen <jani.taskinen@sci.fi> wrote:
> On Thu, 2007-12-13 at 14:36 +0100, Jochem Maas wrote:
> > I would hazard to say that php is becoming a victim of it's own success in
> > this regard - to really tackle the issue would probably require the implementation
> > of a more structured proposal/implementation/release process ... I will grant that
> > that is a mammoth task to undertake!
>
> We already have that, it's called "Feature/Change request" category in
> bugs.php.net (which is of course ignored by everyone :)
Oh. Really? I just added a useful one to fix the stupid way non
optional params are returned as False. Sure it is how it has always
been, but talk about counter-intuitive!
-t[-+] is the proposal by the way with -t- being the default as that
is what is currently done.
Wouldn't break backwards as -+ are not allowed in a param name.
--
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"