.... What I am interested in is: when is it better to sweat over the coding of forth words, squeezing every last ounce of speed out of them at the very likely cost of readability/maintainability, as opposed to just taking the time critical stuff and coding it as C and/or assembler primitives? Cheers Dave Well as cache operates somewhat faster than memory, there comes a ...
... forth words, squeezing every last ounce of speed out of them at the very likely cost of readability/maintainability, as opposed to just taking the time critical stuff and coding it as C and/...to sweat about code before you settle on a design. That way your code will clearly and readably reflect a high-performance design, rather than being built for one design and then partially refactored ...
...-based forths. What I am interested in is: when is it better to sweat over the coding of forth words, squeezing every last ounce of speed out of them at the very likely cost of readability/maintainability, as opposed to just taking the time critical stuff and coding it as C and/or assembler primitives? It depends what the VM is for! When MPE and Forth Inc were working on the OTA ...
... words, squeezing every last ounce of speed out of them at the very likely cost of readability/maintainability, as opposed to just taking the time critical stuff and coding it as C and... idea of rewriting those into a dozen hand-coded assembly instructions. Note that having a clear, readable and commented code at that point really helps in finding out where is the actual bottleneck. ...
.... What I am interested in is: when is it better to sweat over the coding of forth words, squeezing every last ounce of speed out of them at the very likely cost of readability/maintainability, as opposed to just taking the time critical stuff and coding it as C and/or assembler primitives? The first step is to consider different algorithms and data structures. And here, simpler ...
...> forth words, squeezing every last ounce of speed out of them at the very likely cost of readability/maintainability, as opposed to just taking the time critical stuff and coding it as C and/... potentially time-critical parts, and try to come up with a clean design implemented in clean, readable code. When your program is running correctly, you can do timing studies and it should be ...
...: What I am interested in is: when is it better to sweat over the coding of forth words, squeezing every last ounce of speed out of them at the very likely cost of readability/maintainability, as opposed to just taking the time critical stuff and coding it as C and/or assembler primitives? If your code is already fast enough running on your particular Forth on your particular ...
... of forth words, squeezing every last ounce of speed out of them at the very likely cost of readability/maintainability, as opposed to just taking the time critical stuff and coding it as C and/or .... You want to finish your application (if you're writing one), not torture yourself. I'd choose readability and ease of coding over speed. At the same time I like speed too so I use fast ...
...'t be talking about that here. I'm thinking more of DTC, ITC and TTC-based forths. What I am interested in is: when is it better to sweat over the coding of forth words, squeezing every last ounce of speed out of them at the very likely cost of readability/maintainability, as opposed to just taking the time critical stuff and coding it as C and/or assembler primitives? Cheers Dave
...running Outlook 2003 on XP. Would like to improve my outlook so that emails are much more readable on my laptop. current fonts appear size 10 and not too readable.What would you suggest? Readable where? In the Reading Pane or in a separately opened window? What type of message? Plain Text or HTML or Rich Text?...
