RE: [PHP-DEV] PHP 5.1
| From: | David Zülke | Date: | Thu, 03 Feb 2005 22:37:17 +0000 |
| Subject: | RE: [PHP-DEV] PHP 5.1 | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-14601@lists.php.net to get a copy of this message | ||
No offense, but before even thinking about operator overloading support,
really useful and crucial stuff like namespaces or Unicode support should be
tackled first.
David
> -----Original Message-----
> From: Terje Slettebø [mailto:tslettebo@broadpark.no]
> Sent: Thursday, February 03, 2005 11:18 PM
> To: internals@lists.php.net
> Subject: Re: [PHP-DEV] PHP 5.1
>
> >From: "Jani Taskinen" <sniper@iki.fi>
>
> > On Thu, 3 Feb 2005, Terje Slettebø wrote:
> >
> > > Why would it be ok there, but not in PHP? It also exists in other
> scripting
> > > languages, such as Python and Perl.
> >
> > PHP is not Perl or Python or <add-your-favorite-language-here>.
>
> That's not an argument against operator overloading. The question is why
> would it not be appropriate for PHP? Dynamic typing has been mentioned,
> and
> when I said that it exists in other dynamically typed languages, as well,
> I
> get the reply that "PHP is not language xxx". What kind of reply is that?!
> Ilia Alshanetsky suggested in a posting that the PHP community in general
> might not be ready for its safe introduction (i.e. they would typically
> misuse it). I hope it's not the case; after all, it's not such an
> "advanced"
> feature, when several mainstream languages has it.
>
> Regards,
>
> Terje
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>