Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42777
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.231 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=nIvAUzjKRX06cYIOUVEFeWHTYz0oEwkpqy5VaerqtVTlcp2U/ASLoD3RkzMxWI7YCk
         rrhlkbdHtCEw0G8l37U2WuHlNB1jAxdBi+reyNDAnBRujvZ6eCEUXbYKDgtIPJgrnrU3
         4AeM+wEQg2+jj7pwhIxWWFEfUyiKCoQkMTT+8=
MIME-Version: 1.0
In-Reply-To: <fe05d1540901220438j61a09542l773c9a9ae9633b2b@mail.gmail.com>
References: <49778369.4070709@chiaraquartet.net>
	 <1232626789.5728.12.camel@goldfinger>
	 <fe05d1540901220438j61a09542l773c9a9ae9633b2b@mail.gmail.com>
Date: Thu, 22 Jan 2009 11:22:42 -0200
Message-ID: <bcb7aa500901220522v16c5bcecjd3ffc582e03dc5d3@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@php.net>, 
	Greg Beaver <greg@chiaraquartet.net>, 
	PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC lite] implement import of functions in namespace
From: guilhermeblanco@gmail.com (Guilherme Blanco)

Removing an already working feature is just weird IMHO.

Also... this proposal reminds me to an older discussion (please for
God sake, no flaming mails!) that Greg did some time ago that if using
"use class Foo\Bar;" was enough to differ between a static call and a
ns call. It as one of the proposals to solve the :: issue.

IMHO I'm more than happy with something like:

use Foo\Bar as Baz;
$var =3D Baz\myFunc();

There's no need to introduce more weirdness things no 5.3.... let's
just try to get it out of the box and fix the possible introduced
issues.
We're already in alpha3 and I think when switching from alpha to beta
is something like a feature freeze.


Regards,

On Thu, Jan 22, 2009 at 10:38 AM, Pierre Joye <pierre.php@gmail.com> wrote:
> On Thu, Jan 22, 2009 at 1:19 PM, Johannes Schl=C3=BCter <johannes@php.net=
> wrote:
>> On Wed, 2009-01-21 at 14:19 -0600, Greg Beaver wrote:
>>> [RFC]
>>> Implement importing of functions to complement importing of classes and
>>> namespaces.
>>
>> It was aid that import should only work with classes. We might extend
>> that but not for 5.3! The only engine feature to change are closures and
>> there we either get a compromise about the prototyping/OO stuff or
>> commit my patch to remove them for the time being.
>> http://schlueters.de/~johannes/php/5.3-remove-closure.diff.txt
>> (patch is missing the reflection part)
>>
>> It's been a long time for 5.3 already ... let's try to make release
>> cycles shorter, not longer!
>
> There is no pressure on us to push a release. If some features are
> missing to make the new additions complete then let us complete them
> before 5.3.0-final. That's exactly why we have test releases or tests
> phases. It is really annoying to have half backed features
> (caricature) when a final release is fired, and then have to wait .1,
> .2 or .3 to finally get the full working implementation. It is not
> possible to be 100% sure, but for these two cases (closure and this
> one), problems have been identified clearly, let the respective
> developers fix them.
>
> About removing the closure or anything else only because we want the
> beta1 out this month is a bad choice and I strongly disagree with this
> decision (if it happens).
>
> Cheers,
> --
> Pierre
>
> http://blog.thepimp.net | http://www.libgd.org
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



--=20
Guilherme Blanco - Web Developer
CBC - Certified Bindows Consultant
Cell Phone: +55 (16) 9215-8480
MSN: guilhermeblanco@hotmail.com
URL: http://blog.bisna.com
S=C3=A3o Paulo - SP/Brazil