On Sunday 03 July 2005 23:32, Stephen Torri wrote: Beyond the fact that we're quite unlikely to introduce large changes in our base data structures at this point, I fail to understand how what you propose would help at all.
> 1) Move all PropertyMap related template functions to the PropertyMap > class. Since they are inlined template functions working only on the > internal structure inside the PropertyMap object it did not seem > advantageous to keep them in the Event class. The PropertyMap turns an Event into something closer to a java.lang.Object. Given that the PropertyMap is merely a hash set, it's alreay seperated from the Event class. > 2) Simplified the Event interface to the six basic functions > > 3) Inserted the EventDB class But a Segment already is an "EventDB" for all practical purposes. > a: Purpose: Provide the data structure for containing Event class > objects. > b. Internal Data structure: > 1. Map: > a) Key: Memory address of Event pointer (0x40385445) > b) Data: Pointer to Event object You're re-inventing std::multiset<> here, except less efficient because we lose the time-based ordering and the fast search capabilities. > c. Advantage: Eliminates need to have Subordering number. That number gives us a determinist ordering, using pointers wouldn't. -- Guillaume. http://www.telegraph-road.org ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
