Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54653
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CALKFbxvbOaaPkyqTpGrTaDskmhW2beRWhJa4FzFgR1hBjtiGzA@mail.gmail.com>
References: <CAH-PCH5YvyBWfKomU0RaJw2E-GVqPXOV2TZMN9EURfQvYxu54w@mail.gmail.com>
	<alpine.DEB.2.02.1108141452460.4043@whisky>
	<CAF+90c-g8PLVvP2NYMbQcGCjNmPGN7tHdk5B8FpLp6JGik8tYQ@mail.gmail.com>
	<4E481136.3090508@sugarcrm.com>
	<4E483284.4010100@googlemail.com>
	<4E4838E1.3000006@sugarcrm.com>
	<4E48430D.6070409@googlemail.com>
	<4E486A50.4010700@sugarcrm.com>
	<4E48A22E.1040900@googlemail.com>
	<4E48AD3E.6010801@sugarcrm.com>
	<CA+Y0-p8JijO1Dhsqatp7yR+WR0v=V7rQHboPJmHXNFLWVWWGGw@mail.gmail.com>
	<4E48C126.50707@sugarcrm.com>
	<CA+Y0-p9k=8xytDq4t_20ebgE_wv2Nnn4mUpPaYM-1UFBNkCfkg@mail.gmail.com>
	<CAH-PCH4TiMyQOkVGWRRpnezCBeZfJdL2CfLkKec4hsaQ=s79uQ@mail.gmail.com>
	<4E48D848.1070407@sugarcrm.com>
	<CALKFbxvbOaaPkyqTpGrTaDskmhW2beRWhJa4FzFgR1hBjtiGzA@mail.gmail.com>
Date: Wed, 17 Aug 2011 17:15:13 -0400
Message-ID: <CAGovj_O+W3DpSFkfV8LU27cuWzdmsFKgp0H=QpUkrd8M3yri8w@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001636833a84f3029304aab9fd15
Subject: Re: [PHP-DEV] [RFC] Function autoloading through spl_autoload*
From: dmgx.michael@gmail.com (Michael Morris)

--001636833a84f3029304aab9fd15
Content-Type: text/plain; charset=ISO-8859-1

This member of the peanut gallery would like to point out the following
danger.  Consider the following function collection for namespace A.

namespace A;
  function strpos() {}
  function myfunc() {}

Now if I understand the RFC correctly there's an unintuitive problem as
follows - if myfunc is called first, strpos gets redefined for that
namespace and functions as the author might expect for the namespace.  If
strpos gets called first then it will behave as it does in the global
namespace, which may or may not be desirable.  In any event, from where I
stand here in userland, this is potentially confusing.  I'm an amateur of
the 1st degree, but my gut tells me that the behavior state of any given
function should NOT be determined by whether or not a different function was
invoked before it.

On Mon, Aug 15, 2011 at 5:49 PM, Chris Stockton
<chrisstocktonaz@gmail.com>wrote:

> Hello Stas,
>
> On Mon, Aug 15, 2011 at 1:26 AM, Stas Malyshev <smalyshev@sugarcrm.com>
> wrote:
> > Hi!
> > It's not a shortcoming, it was designed that way, and for very serious
> > reasons. If you want to know the reasons, there were discussed
> extensively
> > when namespaces were discussed. Please re-read that discussion. And all
> > things you propose now were already discussed back then too. If you hope
> > people would write \strlen instead of strlen, this discussion is
> pointless
> > because it won't happen.
> > --
>
> I see your viewpoint from a architectural/design perspective and they
> are valid, but I think the impact and design could be lightened with
> some simple rules of precedence.
>
> I think it would be fair to say, autoloader will not be called on a
> function like strpos, or any builtin compiled extension. Only once
> those are cycled through will autoloader for functions be called. At
> this point the performance penalty doesn't exist, because at this
> point the program execution would have halted with a fatal error
> anyways.
>
> -Chris
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001636833a84f3029304aab9fd15--