At 16:46 07.06.2002, Joseph Tate wrote:
>How much of C has been reused, and reused and reused again?  There is no oo
>in stdlib.

Ah come on there is no oo in c.
You should have asked for C++ and STL (and that is very much of code reuse
even though its pro is its main foe: it is so much of reuse that nearly 
none understands it).



To add something here from my point:

- When working alone PHP is fine and Java is oversized.
- However i do like the PHP API very much because a) it is very powerfull 
and b) it does not use oo where that is not needed.

- People here are mixing up thinks they do not really understand:

Java is class based OO -MI +Interfaces
C++ is class based OO
JavaScript is OO without classes but with prototypes.

PHP is something between Java/JavaScript -Interfaces +Aggregation (added by 
module).
It has classes but allows dynamically adding of members.

- When people here ask for private/protected/public this means they want to 
hide some class internal
realisation aspects from derived classes. This is mostly used by workgroups 
where everyone has his own
part and a class protocol (some meber functions and their interaction) is 
designed to allow every group
member to code happily for his own in his area and knowing how to interact 
correctly with the others.

- The above does not affect the ability to dynamically add members. However 
in some cases it offends
class design and in other cases it is a greatly welcomed ability.

(...) bla bla we had that already....

- FIRST: Do we want a language that can be used by workgroups?

- FIRST conclusion (for me): YES if we do not make the language more 
complex to everybody.

Here i must repeat (just follow up the thread and did not remeber who wrote 
it):

AN EXTENSION TO THE LANGUAGE CAN BE IGNORED by those who do
- not like it
- not understand it

It would not be Java because in Java you have no procedural paradigm and 
therefore you are
forced to know every little OO aspect in Java before beeing able to use any 
part of its api.

In PHP oo is only a goodie that can be used so why not making it a good one?

- SECOND:

We want to integrate XML/SOAP (SRM) and so on:

Does anybody who endores this (nearly all here do) believe this is of any 
sense when
not allowing more than one programmer working on the same project? I mean 
hey both
are very complex and it is nonsense believing those features can be used 
alone in
acceptable time.

- SECOND conclusion (for me): We need some more OO features.


marcus


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

Reply via email to