Yes, please don't be discouraged that you need to ask/discuss something,
default privates are considered a good practice but there is no dogma that
says they cant be changed if there are use-cases. In my short time
contributing to Sf2, I have found the whole collaboration thing to be quite
amazing because it really forces you to think out the box and sometimes
other solutions come that are actually much better as a result. (Just my 2
cents worth, in my experience, inheritance is very much over used and
default privates force us to consider other options before just taking the
easy road of inheritance which often, more than not, leads to design and
often compatibility issues down the line).
The Symfony2 community is extremely open and friendly, and everyone is
working to make an excellent basis for the PHP world, so please take the
time to make your use-cases known because your suggestions might help a lot
of people in the future.
Drak
On Friday, 25 November 2011, Tim Nagel wrote:
> The point of the post is that symfony2 will open up things for extension
> when you have a legitimate reason for it.
>
> Discussion is exactly what Fabien wants.
>
>
> t
>
> On Fri, Nov 25, 2011 at 07:16, Arnold Daniels
> <arn...@jasny.net<javascript:_e({}, 'cvml', 'arn...@jasny.net');>
> > wrote:
>
>> 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<javascript:_e({},
>> > 'cvml', '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<javascript:_e({}, 'cvml',
>> 'symfony-devs@googlegroups.com');>
>> To unsubscribe from this group, send email to
>> symfony-devs+unsubscr...@googlegroups.com <javascript:_e({}, 'cvml',
>> 'symfony-devs%2bunsubscr...@googlegroups.com');>
>> For more options, visit this group at
>> http://groups.google.com/group/symfony-devs?hl=en
>>
>
> --
> 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<javascript:_e({}, 'cvml',
> 'symfony-devs@googlegroups.com');>
> To unsubscribe from this group, send email to
> symfony-devs+unsubscr...@googlegroups.com <javascript:_e({}, 'cvml',
> 'symfony-devs%2bunsubscr...@googlegroups.com');>
> For more options, visit this group at
> http://groups.google.com/group/symfony-devs?hl=en
>
--
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
