Hi Lukas, On 10 Mrz., 20:34, Lukas Kahwe Smith <[email protected]> wrote:
> > Why not just put a sentence in the documentation: "protected > > properties/methos are not part of the API and can be changed any time"? > > because that would also not be correct, since we do have places where we > invite users to inherit and reuse methods. that's right. What about public methods which are not really meant to be part of the public API (but need to be public for internal framework use) – do you have a specific way to warn developers that they shouldn't use them? (see http://robertlemke.de/blog/posts/2011/03/11/protected-vs-private for our current approach in FLOW3) Would be perfect to have a common concept / convention for the bigger PHP projects and if we find one, we'd gladly refactor our code to meet it. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
