Be consistent. Avoid premature optimization!

Agreed totaly. But I personally dont count knowning various idioms relative costs as premature optimization. Premature optimization is when you toil over your code for hours to effect a negligable speed improvement that you havent already justified by some good profiling. Knowning the cost of a particular idiom and avoiding those that are expensive for ones that are inexpensive when the time to write either is equivelent is good practice not premature optimization.

:-)

---
demerphq

_{<Elian> And I do take a kind of perverse pleasure in having an OO assembly language...}