CompuServe Messages

Don, >If somebody could just show me how LS is more like adding a 4 barrel >carb and turbo charger to a 2 barrel carbed engine I might go along >with the way LS was marketed. Let me try. If you eliminate one function call and replace it with "inline" code you remove some overhead associated the calling function (pushing values onto the stack, loading CPU registers, etc.). You may only save a few CPU cycles. However, do this in a portion of the code that is executed thousands of times each time the screen is drawn, and you start get visible performance enhancements. Find enough of these kind of opportunities and you can cut the display time considerably. In fact, you can cut it in half. That's it. Find places to save a few cycles inside tight loops and TADA. Liquid Speed. Despite it's simplicity, I had a VERY difficult time deciding what language to use in the marketing of Liquid Speed (without getting into CPU cycles and such). I challenge you to try. If anyone can come up with a compelling message, I'll use it in future LS ads and marketing. >I think we have a 3DS WITH LS at 100% top speed and without it it is >governed to only 50%. Would you mind if I forwarded this message to Autodesk? I think they might take some offense at the implication. Especially since they believe in LS enough to let us put copies of the software in the box with 3DS R4. Best Regards, Brian