Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40369
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain shitennou.com from 208.83.222.18 cause and error)
Message-ID: <48C57761.5030708@shitennou.com>
Date: Mon, 08 Sep 2008 15:05:05 -0400
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Stanislav Malyshev <stas@zend.com>
CC: internals@lists.php.net
References: <ADD0525F-F900-4F3A-9B76-1ED332CA31E0@pooteeweet.org> <486FA5FB.1000300@php.net> <E06A1FB3-971F-4D4F-850A-D0255F7275F7@pooteeweet.org> <48C55855.4080602@zend.com> <A077B6EC-3E30-4F46-91CA-FD75D578CC7A@pooteeweet.org> <48C5624A.1040901@zend.com> <F4.39.33249.21565C84@pb1.pair.com> <48C56743.2060706@zend.com> <48C56821.2040805@shitennou.com> <48C5695E.1010404@zend.com> <48C56A51.1000307@shitennou.com> <48C56CEE.6050807@zend.com> <48C56DED.4010407@shitennou.com> <48C57045.6020003@zend.com> <48C5715C.2070102@shitennou.com> <48C574E8.1030504@zend.com>
In-Reply-To: <48C574E8.1030504@zend.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: towards a 5.3 release
From: auroraeosrose@shitennou.com (Elizabeth M Smith)

Stanislav Malyshev wrote:

>>  If functions in namespaces won't have the same treatment or features as
>> classes why bother ;)
> 
> Functions can't have the same features as classes, because then they'd
> be classes :)

That's not what I meant and you know it (sighs)

Bottom line, being able to alias in functions the same way you can
classes would be useful.  You could also shoot yourself in the foot.

You can alias in classes.  You can shoot yourself in the foot with that
as well.

You can do lots of bad things to yourself in PHP (I'm just waiting until
goto hits...) - I just think that it would be nice to have a common
function (personal use case - a library string translation function)
that could be called over and over again without having to add the
namespace before it.  The other thing this would solve is issues with
ambiguity in namespacing.

<?php
namespace foobar;

function printme{}

class foobar{
static public function printme {}
}
?>

<?php
use foobar::printme as globalprint;
use foobar::foobar;

foobar::printme();
globalprint();
?>

Granted, that's stupid design.  But someone is going to do it, and it is
a workaround rather than forcing the redesign of all the code.

Anyway, this is just one of my issues (and a rather small one) with
namespaces.  Can we get back to autoload problems? (and no text before
opening <?php with a namespace)  And three million use statements?

Thanks,
Elizabeth