On 9/11/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> if the
> file has namespaces, then it can have no code outside namespaces.
This seems like a great compromise, FWIW +1 here.
Does closing php tags end the namespace declaration? ie would the
following work:
namespace foo;
class a
{
pub
etc etc) while PHP doesn't/will not for this release.
Announcing that PHP has package support yet not bundling any actual
packages seems a misnomer.
--
Marc Gear
[EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
rently and just add namespace/package support
> with a serious implementation.
Dont be absurd. All namespaces are is a way of avoiding having to use
Very_Very_Long_And_Very_Irritating_Names. Its why we have separate
scope (namespaces) for functions and classes.
--
Marc Gear
[EMAIL PROTECTED]
groups related identifiers. Classes have their own
namespaces, as do functions. This is adding a namespace to a file,
rather than the whole file being executed in global scope (which is
obviously what currently happens)
--
Marc Gear
[EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development M
here is none.
Purely from a PR point of view, 'namespaces' is going to be a winner
amongst users and 90% of people will wish for a braces implementation,
while 'packages' is likely to generate more demands for something
called 'namespaces'
--
Marc Gear
--
PHP Intern
they usually
> mean logical separation of things in, well, naming space, and when they
> talk "packages" they usually mean files on disk and putting things into
> files and finding which thing is in which file.
You're absolutly right.
+1 here for 'namespaces' (
