Re: Reference Notice
| From: | Wez Furlong | Date: | Mon, 18 Jul 2005 00:47:26 +0000 |
| Subject: | Re: Reference Notice | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-17298@lists.php.net to get a copy of this message | ||
If you think its so easy, why haven't we seen a patch to fix it coming from you?
Now, stop wasting our time with your continued ranting (that applies
to *everyone* who keeps going on-and-on-and-on-and-on about this) and
let us get on with something more productive, which might even include
making this situation better.
--Wez.
On 7/17/05, Robert Cummings <robert@interjinn.com> wrote:
> On Sun, 2005-07-17 at 18:06, Matthew Charles Kavanagh wrote:
> > It's a notice. Your soul won't curdle and fall out of your ears just
> > because your code produces a notice which you can easily prevent from
> > being output.
>
> My soul didn't curdle and fall out of my ears before the notice was
> added either and PHP can easily prevent the memory corruption without
> pissing off it's developer base with inane notices.
>
> Cheers,
> Rob.
> --
> .------------------------------------------------------------.
> | InterJinn Application Framework - http://www.interjinn.com |
> :------------------------------------------------------------:
> | An application and templating framework for PHP. Boasting |
> | a powerful, scalable system for accessing system services |
> | such as forms, properties, sessions, and caches. InterJinn |
> | also provides an extremely flexible architecture for |
> | creating re-usable components quickly and easily. |
> `------------------------------------------------------------'
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>