Difference: ATeamDataContainers (6 vs. 7)

Revision 72007-04-03 - unknown

Line: 1 to 1
 
META TOPICPARENT name="TrackATeam"

Data Containers for Track Discussions

Line: 105 to 105
 

Improvements to PatDataStore concept

Changed:
<
<
The PatDataStore provides a proven fast way of managing data objects. It does though have in my opinion problems with its user interface. The primary one being the inability to use a proper constructor and the potential leakage of data between events. However, it should be possible to improve upon this I think. One possible example is the ROOT TClonesArray class (thanks to Matt for pointing it out) which implements a similar idea but assigns objects to particular memory locations using the placement new method.
>
>
The PatDataStore provides a proven fast way of managing data objects. It does though have in my opinion problems with its user interface. The primary one being the inability to use a proper constructor and the potential leakage of data between events. However, it should be possible to improve upon this I think. One possible example is the ROOT TClonesArray class (thanks to Matt for pointing it out) which implements a similar idea but assigns objects to particular memory locations using the placement new method, and is something we could look at (NOTE : I am NOT suggesting using the ROOT TClonesArray directly...)
 

Custom allocators

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback