Also, if we loosen the encapsulation provided by the package access specifier so that it allows access also to modules in nested packages, then why is this keyword even named "package". Newcomers to the language would be asking us why is this keyword names "package", when it provides access beyond the package where the module is in. Loosening the encapsulation provided by 'package' is not logical nor called for.

Reply via email to