Re: Namespaces in PHP 6 - ++$take
| From: | Robert Cummings | Date: | Sat, 11 Nov 2006 01:57:49 +0000 |
| Subject: | Re: Namespaces in PHP 6 - ++$take | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-26510@lists.php.net to get a copy of this message | ||
On Sat, 2006-11-11 at 00:31 +0100, Marcus Boerger wrote:
> Hello Hans,
>
> Friday, November 10, 2006, 8:30:55 PM, you wrote:
>
> > Brian Moon wrote:
> >>> Unfortunately namespaces are not only syntactic sugar, but dire
> >>> necessity
> >>> for PHP if it wants to be taken as a serious langauage and defend it's
> >>> position against other arising 'web scripting' alternatives.
> >>
> >> It seems the list of things that PHP needs to be "taken as a serious
> >> langauage" is never ending. Before PHP 5, all that was needed was
> >> good OOP support. Now this. I am for namespaces, but that line is
> >> getting old and I, a professional, serious PHP developer and tired of
> >> hearing it.
>
> > I think that one reason why this list is never ending is that these
> > languages are constantly moving targets -- I would hope that what people
> > expected of a web development language would evolve over the course of
> > several years. Daniel's project (coWiki) was one of the first (if not
> > the absolute first) to show us what was possible with PHP5 and
> > Exceptions; that was some pretty serious PHP. I think what Daniel means
> > is that to remain competitive, PHP needs to include the features that
> > developers have come to expect of a language
Many developers came to PHP in spite of what other developers had come
to expect in other languages.
Cheers,
Rob.
--
.------------------------------------------------------------.
| InterJinn Application Framework - http://www.interjinn.com
|
:------------------------------------------------------------:
| An application and templating framework for PHP. Boasting |
| a powerful, scalable system for accessing system services |
| such as forms, properties, sessions, and caches. InterJinn |
| also provides an extremely flexible architecture for |
| creating re-usable components quickly and easily. |
`------------------------------------------------------------'