>> How willing are you to trade simple code for longer, more optimized code?
>Extremely, if warranted. When rewriting code to use greater performance optimizations, the original code should remain available, as a drop-in replacement for the optimized code. E.g., you might have files like:
>foo-knowngood.c
>foo-optimized.c
Pardon me if I am naively misunderstanding you, but are you suggesting that we should maintain two separate code-bases? That seems tedious, but I'm not a professional software engineer, so maybe this is standard practice for you guys.
>> How willing are you to
>> How willing are you to trade simple code for longer, more optimized code?
>Extremely, if warranted. When rewriting code to use greater performance optimizations, the original code should remain available, as a drop-in replacement for the optimized code. E.g., you might have files like:
>foo-knowngood.c
>foo-optimized.c
Pardon me if I am naively misunderstanding you, but are you suggesting that we should maintain two separate code-bases? That seems tedious, but I'm not a professional software engineer, so maybe this is standard practice for you guys.