Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41226
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.132.251 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
         :content-type:references:x-google-sender-auth;
        b=A635XNJ5w8gMJ8jorSLQH4FW62kkuOSSHzljeS8AyQv3MCxL4ZYsWDPgVeSiax6+IX
         g4m0At28K1dP7CE/M8253m+cFYSAKaOXLtNAG9fY5729MhxxrdjXJVZXXODFN5998NW5
         cIuCA8vYXGi2Lvz7+bJPazP7NpiUHOpvTnQko=
Message-ID: <622403340810170833k562d313er6adbdfb1842fc05b@mail.gmail.com>
Date: Fri, 17 Oct 2008 10:33:33 -0500
Sender: nate.tallman@gmail.com
To: "Ryan Panning" <rpanning@gmail.com>
Cc: internals@lists.php.net
In-Reply-To: <63.BA.57950.BB2A8F84@pb1.pair.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_66659_32970768.1224257613203"
References: <48F653FF.5010106@chiaraquartet.net>
	 <63.BA.57950.BB2A8F84@pb1.pair.com>
Subject: Re: [PHP-DEV] Re: my last attempt at sanity with namespaces
From: nate.tallman@connectivhealth.com ("Nate Tallman")

------=_Part_66659_32970768.1224257613203
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

+1 #3

On Fri, Oct 17, 2008 at 9:35 AM, Ryan Panning <rpanning@gmail.com> wrote:

> Greg Beaver wrote:
>
>> Hi,
>>
>> http://wiki.php.net/rfc/namespaceissues
>>
>> Read it and discuss.  Let's be clear people: the technical problems in
>> namespaces are limited and solvable.  The problems in the political
>> environment surrounding them may not be.  Wouldn't politics be a
>> stupid-ass reason to remove namespaces?
>>
>> Greg
>>
>
> Issue A: #2
>
> Issue B: Yes
>
> The reason I like #2 is because it also helps with the autoload confusion.
> It will clearly state that you are either looking for a class or namespace
> file, by looking for the element separator. However, I think :> or something
> other than ::: would be a better separator, for better visability. Ex:
>
> Request              Autoload Gets   Type
> -----------------------------------------------
> A::B:>C              A::B:>C         Class
> A::B:>func()         A::B            Namespace
> A::B:>C::CONST       A::B:>C         Class
> A::B::C:>D::method() A::B::C:>D      Class
> A::B::C::D:>CONST    A::B::C::D      Namespace
>
>
> Question for issue B, will the change only effect class requests? Or would
> it also trigger autoload for function requests (thinking it's a namespace
> request)? I could see that being a problem as 90% of function requests are
> for internal functions and ::func() for everything would be a pain.
>
> Similar goes for namespace function/const requests. At this point it
> wouldn't be a big deal but lets say core internal functions are migrated to
> namespaces (ex: Array::map()). Does that trigger autoload before it finds
> the internal Array::map()? I'm thinking that's where option #3 comes into
> play, but "using .." every internal class/ns/func would also be a pain.
>
> Sorry if this was already answered, I've been trying to keep up. :)
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

------=_Part_66659_32970768.1224257613203--