Re: Event_Dispatcher request

Stephan Schmidt wrote: >Hi, > >Bertrand Mansion wrote: >> Unless there is a good example of where this can be used, I am strongly >against >> opening access to $_ro and allowing people to mess with it directly. Adding or >> removing observers should be handled by using the class methods (which is the >> case right now), not by playing with $_ro directly IMO. Of course, that's >unless >> I'm missing something... >I can't see a problem in *reading* the list, I will also *not* add >something for write access. In a Java framework where I'm using a >similar package I need the fetch all listeners for debugging purposes >and I guess it wouldnt' hurt having this feature in Event_Dispatcher. If by reading you mean something like toString() or toArray(), then it's fine with me. To debug Event_Dispatcher, it's also possible to have a listener that listens to all the notifications and log them somewhere. Bertrand Mansion Mamasam