-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
6
The CMSCollector constructor has grown quite large and somewhat unweildy.
Part of the reason is that ancillary data structures needed by the
CMS collector are constructed in-line and failure to allocate such
data structures requires some amount of clean-up. Such code should
be better encapsulated and moved to individual c'tor/init()/d'tor
methods, so as to clean up the CMSCollector c'tor, and so that,
as a matter of hygiene all these structures are destroyed when
the CMSCollector is.
Part of the reason is that ancillary data structures needed by the
CMS collector are constructed in-line and failure to allocate such
data structures requires some amount of clean-up. Such code should
be better encapsulated and moved to individual c'tor/init()/d'tor
methods, so as to clean up the CMSCollector c'tor, and so that,
as a matter of hygiene all these structures are destroyed when
the CMSCollector is.