So what about using @triggers (like @throws) instead of @event? I see @Event "annotation" is used for example in \Symfony\Component\HttpKernel\KernelEvents for describing class related to event's name and I think it's better usage for it.
I'm sorry for digging it out since it's old thread, but I came here from google results and don't know if it's closed :-) W dniu czwartek, 18 października 2012 20:09:48 UTC+2 użytkownik Niels Braczek napisał: > > Am 18.10.2012 16:49, schrieb Drak: > > > In the end, the same is true - listeners are notified of something > > happening which does not require they specifically do something. It's > very > > much passive. Notification is passive. Triggering is not. > > It's not about listeners, it is about events. > > The listeners are not known at development / documentation time, since > they are added at runtime. Thus, the *notification* of any specific > listener is not documentable/relevant. What needs documentation is the > event (or signal) that is *triggered*, so a developer / an IDE can see, > which events a listener can react on. > > Regards, > Niels > > -- > | http://barcamp-wk.de · 2. Barcamp Westküste Frühjahr 2013 | > | http://www.bsds.de · BSDS Braczek Software- und DatenSysteme | > | Webdesign · Webhosting · e-Commerce · Joomla! Content Management | > ------------------------------------------------------------------ > -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/87cad7e1-56b3-495f-84bb-c941c05f23c3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
