Hi, It's a good post. That doesn't mean I agree with it.
Anyway, I won't start a discussion here, since you're probably not looking for it. I just have to stick with copy/pasting all the code for a class :s - Arnold On Thu, 2011-11-24 at 11:25 -0800, Fabian Spillner wrote: > Fabien wrote a good blog post about Private vs. Protected: > > http://fabien.potencier.org/article/47/pragmatism-over-theory-protected-vs-private > > > > On 24 Nov., 12:49, Arnold Daniels <arn...@adaniels.nl> wrote: > > Hi all, > > > > First of all, thanks for your time to read and respond this e-mail. > > > > I'm working on an extending Symfony, overwriting some of the > > generators behaviour. Unfortunately extending an existing class like > > DoctrineCrudGenerator doesn't work well because all properties and > > helper methods are private. This makes it impossible for me to > > overwrite a single method, leaving the rest of the code in place. > > > > I was wondering what the reason is behind making the properties and > > methods private instead of protected? > > > > - Arnold > -- 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
