why there is no way NOT to implement at least private and public types...

I hope Zeev, Andi & Co. are listening. Since PHP4 takes it´s OOP awareness one step further, many problems arise. Distributed programming on large projects will become easier (and easy), polymorphic, multi- langual projects will grow and programmers do want to protect their data. But they cannot (currently), they do have to secure their methods and object data to prevent a) illegal accessing of methods and b) illegal data spying (eg. passwords) and c) overwriting and overriding data and methods from external and so on... I know there is a lot of things to do - compiler, cache, killing remaining php4 bugs, implementing the (20?) remaining levels for the optimizer... but I think after having killed the remaining php4 bugs someone should think of implementing such OOP stuff. I remember Andi once said PHP will never be a fully OO language, maybe, but I think (and I hope) protecting inner data should be possible. The functionality of PHP has grown a lot through OOP and mega-projects will get the needed rest of power with the zend.cache and zend.compiler and will be (hopefully) invulnerable to reverse engineering, but truly distributed programming needs a special protection. andré