On Mon, May 2, 2011 at 9:40 PM, Johannes Schmitt <[email protected]> wrote: > One of the the pros for these Events classes is that you have > auto-completion for which events are available. That's really the only > purpose these classes serve, and imo it is a good thing. > > However, there is a chance for conflicts, but I think this is more a > documentation issue; we probably have to create a naming convention for > events to make sure people do not create conflicting names.
Well ok but why not have the strings just be event identifiers, so they can be long and namespaced and whatever, and then we attach listeners with an identifier + a callback. Why is there this method name = event identifier restriction? Cheers -- Jordi Boggiano @seldaek :: http://seld.be/ -- 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
