AW: AW: [PHP-DEV] Namespace resolution
| From: | Matthias Pigulla | Date: | Tue, 11 Dec 2007 23:03:00 +0000 |
| Subject: | AW: AW: [PHP-DEV] Namespace resolution | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-33940@lists.php.net to get a copy of this message | ||
> Von: Stanislav Malyshev [mailto:stas@zend.com]
> But you could achiever
> the same just by avoiding naming classes the same as internal classes,
> you surely know which classes are in your own namespace?
...
> Not using names of classes same as internal classes is not a big deal
> either - all PHP programmers do it right now :)
Rumor exists that sometimes new internal classes show up in late RCs. And as you try to name your
classes so that the name describes the modeled construct best, it is not surprising that core wants
to name such a new class "Date" just as userland folks had their classes named
"Date" as well before (shame on them).
I always thought that one of the prime reasons for providing namespaces was to mitigate this risk of
breakage in a simple, predictable and user-friendly manner.
-mp.