RE: [PHP-DEV] parent_ctor()
| From: | David Hjortso | Date: | Mon, 17 Jul 2000 16:53:44 +0000 |
| Subject: | RE: [PHP-DEV] parent_ctor() | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-24789@lists.php.net to get a copy of this message | ||
Hi,
> If you're forced to do it in Java because you don't like the OO
> implementation of PHP or it's not powerful enough for you, then
> it's *NOT* sad at all that you'd use Java. You can't say "I want to do it
> in PHP, but PHP can't do it at all and its entire implementation and
concept doesn't
> work this way, so I'll do it in Java". If you want the Java OO model and
> approach you want to do it in Java, period. Don't change PHP to be what
> it's not and not supposed to be; Use the right tool for the right job.
It made sense to me :)
What I mean is that I enjoy ALOT of the functionality that PHP has, making
it quite easy to manipulate data, and I will miss those if I have to go for
java instead of PHP. As you can see by the list I made, I don't find the
missing things -- except for the serializing-reference problem -- a big
problem.
I don't think I am trying to bend PHP to something that it is not, since
there are heaps of java stuff that I will never need, but there are heaps of
PHP functionality that i WILL need, and that java CAN provide though not as
easily as PHP.
I completely agree that PHP shouldn't try to be everything, and I am not
trying to make it be, I am just trying to see if it's possible to get *the*
functionality (again, my point of view...yadda...yadda...) that *I* need to
push PHP as *the* language of choice for the projects I am making, and I
don't think that the changes/problems I have mean that PHP should be
everything.
Might be wrong though :-)
Kind regards,
David Hjortsoe.