CB>1) although on your computer and compiler, pointers are faster than
CB>direct indexing, they may not be on other peoples computers and
CB>compilers.  This will depend on compiler optimizations available, the
CB>register assigning the compiler makes, and the individual CPU itself.
So you are happy to let an optimizer do all the 'hard-stuff' for you? I for 
one, am not, and compile my programs for specific machines. Multi-processor 
programs should be compiled specifically for the machine intended, to gain 
the absolute fastest performance. I wouldn't mind 20 or so different versions 
of the executable on a compact disc taking into consideration that the 
programmer was nice enough to make a program run for YOUR computer, not this 
'if it doesn't work, get a better machine' attitude I keep seeing all over 
the place when it's quite obvious that performance performed by games such as 
quake could be atleast 20% faster on a 486 using the appropriate An 
optimization optimizers certainatly can't do is Code Patching, which 
increased performance of an affine texture mapper of mine by almost 50%.
... For sale: Hourglass for timing Windows.
--- Ezycom V1.48g0 01fd016b
---------------