Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41700
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fmethod.com from 69.16.228.148 cause and error)
Message-ID: <D1415A3C2B0A4FC5B068A43E92C40090@pc>
To: <internals@lists.php.net>
References: <29.7A.15458.C4880194@pb1.pair.com> <5C.FA.15458.9A980194@pb1.pair.com> <A4F5DBE2-7F83-4C24-8B7D-8D9C9CCE8552@pooteeweet.org>
Date: Thu, 6 Nov 2008 00:46:40 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="ISO-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Namespace Resolution
From: sv_forums@fmethod.com ("Stan Vassilev | FM")

> Here are some reasons why we felt that functions/constants should 
> fallback:
> - most namespace users will be using classes and not functions

This is a self-fulfilling prophecy, the more you open a gap between classes 
and functions, the more people will stick with the richer functionality 
since it's just too much hassle to bother with two different paradigms.

Case in point: do you know a major reason why people keep using static 
methods to "fake" functions? It's not as much to namespace it. I mean 
Foo::bar() or Foo_bar(), who cares? It's all the same.

But the big difference is, I don't have to explicitly load the function 
library if it's a static class. Classes have autoload, functions 
mysteriously don't. Hence, even I have abandoned using functions today and 
use fugly static method hacks. It's less hassle to do it wrong right now, 
than do it right. So I do it wrong.

Namespaces won't change any of this, since I still can't autoload my 
function library.

Regards,
Stan Vassilev