Well, not keen to add fire to this argument, but I can say that my game won't run full speed without look up tables.
Let's see, there's a heat haze effect, needing two passes, one with about 350 cos operations and about 250 sin operation per frame.
If however your target market is the 386SX, OR YOUR MAIN LOOP AND PROGRAM CODE CONSISTS LARGELY OF SIN AND COS CALLS, BY ALL MEANS USE LOOKUP TABLES. For 99% of people, the performance difference will be negligible, or possibly worse.Let's see, there's a heat haze effect, needing two passes, one with about 350 cos operations and about 250 sin operation per frame.
I think 350 cos and 250 sin operations would fit exactly for that situation.
Most people however are not doing anywhere near that many calls in a loop.
Code should be profiled on a situation by situation basis and there is no uniform, one shot method of making fast code.