Sara Golemon schrieb:
> All the added functionality of namespaces without all the baggage.
+1
--
Sebastian Bergmann http://www.sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
--
PHP Internals - PHP Runtime Development Maili
I personally never use constants anyway. But at least functions and
variables should work with namespaces:
namespace name1 {
$var = 3;
function func();
}
From a language perspective those should exist only in that namespace.
I also think '\' as a seporator is nice. It has this nice filesys
Jessie Hernandez schrieb:
> I think this is the best solution thus far. If any one of you still feels a
> need for constants/functions, PLEASE show me a _valid_ example that cannot
> be accomplished by just simply putting the constant/function inside a class
> in the namespace.
No complaints from
Hello Sara,
Please explain what the difference is between nested classes, and
this type of namespacing?
If you scrapped namespace constants and functions, then all we have
left is classes. If it was looked at as nested classes, then we get
all the functionality with all the simplicity
> So, the question is, can we scrap both namespace constants and namespace
> functions and just stay with classes (as was agreed on several months ago,
> Andi himself agreeing to it)? This would make the patch smaller, simpler,
> AND would allow me to reuse the "::" operator (and there would be no
