PHP has namespaced package support.
Yep, that's what I was talking about. "We have namespaces but we call it packages because Java does". Eek.
Wikipedia also define the term MVC. But alas, that is a conceptual definition, not blueprints for implementation.
Who cares about the implementation? It's still MVC. So let's implement MVC and call it "distributed enterprise messaging" and then let's spend next 2 years explaining that it was really MVC that we meant.
namespaces and packages. But the general taste this will leave in peoples mouthes is package, even if it is a Grapple.
I am still waiting to know what is package? I know what is namespace - and I for everybody that doesn't know I can explain it in 2 minutes with one hand tied behind my back. But what is "package"?
current implementation doesn't have braces; this (consequently) adds a
Ouch, not braces again. What is it with braces that you need them so badly? Many languages aren't using the things ever, isn't it a proof that there's life outside braces? ;)
library "packages". Point in case is how the ZF has used a pesudo-namespace-ing class name to accomplish the very same thing.
ZF is using Very_Very_Long_And_Very_Irritating_Class_Names because there's no choice to do otherwise. That's why we wrote namespaces - to provide this choice.
+1 on package, it makes the most sense regardless of the marketing draw of "namespace" support.
Please re-read my mail on perception. "Marketing" here is just a way to say "perception" so it sounds bad to some people for some reason.
-- Stanislav Malyshev, Zend Software Architect [EMAIL PROTECTED] http://www.zend.com/ (408)253-8829 MSN: [EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
