>From: "Jani Taskinen" <[EMAIL PROTECTED]>

> On Thu, 3 Feb 2005, Terje Slettebø wrote:
>
> >> From: "Jani Taskinen" <[EMAIL PROTECTED]>
> >
> >> 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?!
>
>      Quote from your mail:
>
>      "Why would it be ok there, but not in PHP? It also exists in other
scripting
>      languages, such as Python and Perl."
>
>      Please explain me why it's okay for you to use the
other-languages-card
>      but not for me? :)

Ok. The argument went something like this: I asked (although that was
originally in another thread) about the possibility of getting operator
overloading in PHP, and I presented reasons for why this may be useful. Then
someone replied that PHP is dynamically typed, so it "doesn't fit the
language". I countered with that there are other languages that are also
dynamically typed, but where they do have operator overloading. Now, if the
"doesn't fit the language" argument should stick, one could need to either:

1) Explain why it's a bad idea in these other languages, as well, or:
2) Explain how PHP is different, and why it doesn't fit PHP, unlike these
languages.

Now, have I got any answers to this? No! All I've got (from your posting,
anyway) is "PHP is not language xxx". And? How does it change the argument?
In what way is it different, so that operator overloading would not fit with
PHP? I've got some answers in this thread, and I'll also search the archive
for the rest, but "PHP is not language xxx" is a meaningless "answer".

My use of the other languages was to show that other languages find it
useful. Your use of other languages... well, it only says that PHP are not
them, which doesn't really say anything beyond the obvious. I'm sorry, but
our two arguments can't be compared.

>      Please, end this thread already and face the fact that this feature
>      will not get into PHP 5.1.

I have no illusions of it going into PHP 5.1... This wouldn't be appropriate
for a point release, for one thing.

I have also very little belief of it ever getting into PHP, judging from the
discussion.

Regards,

Terje

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to