On 03/29/2003 04:36 AM, Andi Gutmans wrote:
We won't support this. (btw it's the default modifier in Java if you don't write anything else).
I am not defending or suggesting that you support it, I am just asking if you will. BTW, what is the reasoning for supporting private, protected and public, but not package (namespace?!)?
private/protected/public are topics which most people who have used OOP in the past understand well. Package level access tend to be much more confusing and aren't as common. That's why I see a difference.
I don't see what is so confusing in only allow to access the members of a class from another true class that belongs to the same package.
Anyway, your reasoning is interesting because while you justify not adopting a protection level that is useful to people that develop packages with several classes (think of many of the packages in PEAR if not anything else), you add things that seem much more confusing and less useful like nested classes and interfaces!?!
-
Regards, Manuel Lemos
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
