Re: [PEPr] Comment on PHP::Debug

Lukas, > Basically with "protected" you are being "friendly" to extending, but it > also means that you now have committed to a certain API. Since we do not > allow BC breaks in the same major version number, the default should > probably be "private", although authors are very much encouraged to work > on making as much "protected" as possible (and certainly anything that > is necessary). Is api stability for "external" users that just use the class, or is it also meant for the inner workings -> protected methods? If the first, then we'd need two api stability levels. But: Maybe I cannot make a method private since I use it in my package in an extending class. What then? If I re-release the package, I will make sure that all classes work together, after changes in inner workings or re-organization. But I cannot gurantee this for other projects that extend my class. The public api is still stable, but extending classes will break. -- Regards/Mit freundlichen Grüßen Christian Weiske

Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc