> There is piece of code in DEBUG mode that makes sure that order is right, if
> it is not it does fires an ASSERT. That prevents the problem from happing
> again. In my version, I do not need to compare as many times and as elements
> are in release mode to find out the next element. I prefer to make an effort
> that to waste user's CPU cycles.
There are about 65 dialogs. Inserting happens solely at startup time.
I don't think that we're "wasting" many CPU cycles. I wouldn't worry
about wasting .01ms of startup time. If your solution ensures
correctness via an ASSERT, than great. If not, it needs to be
reverted.
Cheers,
Dom
Received on Wed Jul 11 17:25:15 2007
This archive was generated by hypermail 2.1.8 : Wed Jul 11 2007 - 17:25:15 CEST