Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17287
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals@lists.php.net
Content-Type: text/plain
Organization: InterJinn
Message-ID: <1121626339.23752.24.camel@blobule.suds>
Mime-Version: 1.0
Date: Sun, 17 Jul 2005 14:52:19 -0400
Content-Transfer-Encoding: 7bit
Subject: Reference Notice
From: robert@interjinn.com (Robert Cummings)

I think the reference notice stuff is a bit ridiculous. I mean I can
understand the concern behind:

    function &foo()
    {
        return $fee.$fii;
    }

But I mean the following gives errors too which is a bit too anal
retentive even for my liking:

    function &foo()
    {
        $fee = 'bullshitBullshitBullshit';
    
        return $fee;
    }
 
    function &fee()
    {
        return foo();
    }
 
    fee();

Anyways my two cents. Seems moronic that I now need to worry about
stupid reference notices X levels deep in the code for functions that
I'm consuming. I gueeeeeeeeeeeeess I can assign return values EVERYWHERE
to temporary variables just to get rid of the notices, but really,
shouldn't the engine be happy enough returning references to it's own
intermediate variable? I mean, heck, the engine knows enough to print a
warning, it can do the work-- and a hell of a lot faster than developers
having to temporarily assign everything.

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.          |
`------------------------------------------------------------'