Am 11.03.2011 23:00, schrieb Bulat Shakirzyanov: > If you spot a case where you want to get ahold of a private > property/method, please make your case > and we will either tell you how to do it best using existing means, or > open up the above-mentioned > member to inheritance. > I have seen this argument a lot. Have you checked lately how many issues on the tracker of doctrine 1.2 for example have not even been read/commented by a developer in the last half year because all efforts go to doctrine 2.0? Today when everything is new, those changes will be done quickly. But later? And I do not expect a developer searching for a solution will want to wait for some months for a change, and be dependent on the good will of a developer. So this probably means that you have to use your own git clone then. And I am not sure how easy this is if you are using another SCS for your own projects. Generally I feel that a developer should be able to use the whole framework as he/she sees fit, and not like the framework developers expect it's best for him/her (which it certainly is in most cases, but not in all).
-- 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
