Hello Matthew,
> If you're talking about the _protected_ property, or the fact that many > setEventManager() implementations use "$events" as the name of the > EventManager property, or even that many examples will use constructs > like "$events = $object->getEventManager();" it's simply because: > > a) it's shorter to type > b) it has a semantic affinity to how other languages (esp. JavaScript) > refer to event collections/managers. But it doesn't reveal what it really is - it is not a list of events, it's an instance of EventManager . . . ! Why is the EventManager class then named EventManager, not Events? > In JavaScript, you typically work with an "events" collection, and > attach/trigger from that; we chose terminology that should be familiar > to those familiar with that paradigm (which will be a majority of web > developers). Still, it's an event manager. Best regards, Andreas -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
