Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40814
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.200.169 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:references;
        b=Al24XuqnMSuqxy5qPVu2wJaPOKSOa03P0MpqA/hig+UWuWLcNoLmGl/7RI+Hx+u8Pb
         k8vpW+foE6xTXavpy0AH6tImYttqgtWAEHSrZmH3oZGJQhDF+fjN0kVf5cHX3+2hFnga
         5LR7twp1zSmp4YCYr/KqwmJXwwHeP3W5BCtSQ=
Message-ID: <261daaa10810010034o26b58c0el3fdda5a7b32a04f5@mail.gmail.com>
Date: Wed, 1 Oct 2008 10:34:35 +0300
To: "Stanislav Malyshev" <stas@zend.com>
Cc: "PHP Internals" <internals@lists.php.net>
In-Reply-To: <48D7F5EF.3090202@zend.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_30280_8438110.1222846475633"
References: <48D7F5EF.3090202@zend.com>
Subject: Re: [PHP-DEV] namespace issues
From: kenashkov@gmail.com ("Vesselin Kenashkov")

------=_Part_30280_8438110.1222846475633
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I'm -1 for "removing constants and functions from the namespaces". As I
wrote already in another thread, is it possible to have a fatal error thrown
when the engine detects an ambiguity situation? Are there any logical (i
mean from OOP point of view) or internals (performance and so on) problems
with this solution? In my opinion is better than dropping funcs & consts.

Vesselin Kenashkov

On Mon, Sep 22, 2008 at 10:45 PM, Stanislav Malyshev <stas@zend.com> wrote:

> Hi!
>
> On the ZendCon, we (Marcus, Elizabeth, Andi and myself) had a talk about
> what we'd like to do with namespaces, and we arrived at the following
> conclusions, which we propose to implement in 5.3:
>
> 1. Allow braces for namespaces. So, the syntax for namespaces will be:
> a) namespace foo;
> should be first (non-comment) statement in the file, namespace extends to
> the end of the file or next namespace declaration.
> b) namespace foo {}
> can appear anywhere on the top scope (can not be nested).
> Mixing both syntaxes in one file is not possible. The semantics of both
> syntaxes will be identical.
>
> 2. Simplify resolution order for classes in the namespace: unqualified
> names are resolved this way:
> a) check "use" list if the name was defined at "use", follow that
> resolution
> b) if not, the name resolves to namespace::name
> Consequence of this will be that for using internal class inside namespace
> one would need to refer to it either as ::Foo or do use ::Foo prior to its
> usage.
>
> 3. Functions will not be allowed inside namespaces. We arrived to
> conclusion that they are much more trouble than they're worth, and summarily
> we would be better off without them. Most of the functionality could be
> easily achieved using static class methods, and the rest may be emulated
> with variable function names, etc.
>
> Comments?
> --
> Stanislav Malyshev, Zend Software Architect
> stas@zend.com   http://www.zend.com/
> (408)253-8829   MSN: stas@zend.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

------=_Part_30280_8438110.1222846475633--