Hi Andreas, I hope I don't end up confusing the issue here, but I'd like to offer one explanation for the naming (at least as I've used it).
There are two different contexts by which I'll look at any library component when I'm building a system. During the analysis phase, I only consider the behavior of each component rather than the values it may or may not contain. In this case, the EventManager is a class which manages an untyped collection of labeled callables, and decides what to do with them during run-time. With my own naming convention, I almost always call this type of class a manager because it is so much easier to understand in my class diagrams. However, when I'm actually coding, I switch to a run-time method of thinking. I'm not as interested in the EventManager object itself, but rather the collection of events it contains, so I naturally just call the instance 'events'. It can definitely be confusing if you're frequently switching between role of the analyst and developer, but I've personally found it to make things much clearer for me in the long run. (just my 2¢) Cheers, -Matt P. -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/Events-vs-EventManager-tp4658013p4658049.html Sent from the Zend Framework mailing list archive at Nabble.com. -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
