If you are using maps when linked lists will do, the bloat isn't in the code. If you are using linked lists when maps are indicated, the performance is going to be slow. For moderate amounts of dynamically changing data that need to be looked up, maps are good unless you have unlimited amounts of programming time. I have used STL maps in a soft real-time environment and they were not the bottleneck and they shaved at least a month and a bunch of bugs off my schedule. Use the right tool for the job and remember what the real limited resource is. Maybe the programmer's time? Otherwise we would all still be working in machine language.
Just my 0.02USD, Jeffrey Quoting Andy Kopciuch <[EMAIL PROTECTED]>: > On Wednesday 06 February 2002 15:39, Sean 'Shaleh' Perry wrote: > > There has been some concerned raised and I want to discuss this on its own > > thread so no one misses it. > > > > In the upcoming weeks there is going to be a major change in the blackbox > > internals. Part of this is to remove the home brew linked list code and > > use the STL. Part of this is to allow for support of the NET WM spec > > (compliance with KDE and eventually GNOME). Part of the effort is simply > > refactoring which happens to code every now and then as part of its life > > cycle. > > > > I am assuming you have done some serious investigation into using the STL > containers in Blackbox.
