> Obviously there is a little penalty in calling the compare procedure
There
will be a little penalty, because you need a few steps to call the procedure; but most of the time is being spent on the algorithm of the coder. Not matter how efficient he/she will code, it will take a certain amount of time.
It would be interesting to hear,
which algorithm PB uses to sort the content. Can you tell us, PB team? I can imagine, that there are algorithms that are efficient, but need much less steps than other algorithms.
In other words: the less steps the internal sorting algorithm needs, the more time can be spent on the callback; the time needed will be the same as using no callback and an algorithm that takes more steps.
Hope, you could follow me.
> But personally I don't consider it a problem
Me too.
PackMemory(), for example, also accepts callbacks. I bet, a callback there also creates a little penalty, however, you would never get the idea that the (de)compressions takes much more time, just because of the callback.
> Maybe there are sort routines like that in the forum too
Well, it would be neat to have this natively implemented.
That's the reason for posting it into the feature request subforum. If we always take any codes from the forum, we could close the feature request subforum.
