Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31254
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.184.234 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=hiOa2uYr7ShVodymcm0Nc+HNL8Oo/bgqMqFnn7gegfUKTk52WiTaJ0FI6POIwIX/ZyowtwN+v0EIcZqPv/qUdB5m/rpCYBh7rXX11V1eSovyCEp3hiYFgs9M2MQdUjSbGXydEgcP9SebgB5/7+OOPSEz1C4Qg9347QtkE6BrYbU=
Message-ID: <99cd336d0707241832u14e2cfecx8cea4a46b744ab0@mail.gmail.com>
Date: Wed, 25 Jul 2007 11:02:53 +0930
To: "Stanislav Malyshev" <stas@zend.com>
Cc: "=?ISO-8859-2?Q?Pawe=B3_Stradomski?=" <pstradomski@gmail.com>, 
	internals@lists.php.net
In-Reply-To: <46A6A54E.5040004@zend.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46A31D95.2080407@fischer.name>
	 <200707231140.55535.pstradomski@gmail.com>
	 <46A4BA4F.6090506@dealnews.com>
	 <200707231643.22562.pstradomski@gmail.com> <46A4D07A.7060006@zend.com>
	 <99cd336d0707231952l18dfde71pee6647bb80cf50c6@mail.gmail.com>
	 <46A6A54E.5040004@zend.com>
Subject: Re: [PHP-DEV] Question about Namespace patch
From: slackmase2@gmail.com ("Andy Mason")

Well i'm not in favour of the importing of everything , i don't see
the need for it personally but others do, as you well know. I was just
trying to find a way to achieve everyone goals without sacrificing
speed or correctness for those who want it =)

Shame about the single file thing though. I'm out of ideas, so best of luck :)
Andrew

On 7/25/07, Stanislav Malyshev <stas@zend.com> wrote:
> > Is this something that you would consider for PHP ?
> > As far as I can tell from the list the two main considerations are not
> > pushing the decision to the executor and it being simple.
>
> I can consider it as much as I want - and applications like Zend
> Framework do work this way - but I also know not everybody works this
> way. In fact, I get requests right here for having all code of whole
> library handled as single file...
>
> > The only downside is that this now requires a 1 class / file. This
> > IMHO isn't a massive problem as long as it can be explained, and those
> > who have the task of splitting this up now can do an import Foo::*; ?
>
> I don't see any imports involving * happening, since they all have a
> common problem - you don't know what you are importing. Fortunately,
> they also are completely unnecessary - if you need all things inside
> Foo, why won't you just refer to them as Foo::things?
> --
> 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
>
>