...little reason not to use 16 bit addressing, a simple process of inserting 3*1/2 cells (on 32 bit) for a long jump would reduce most DTC pointers to half a cell. (This assumes people clever enough to place small kernals every so often in memory, or use the vocabulary system to split code into convienient blocks). On silicon stack machines, Chuck Moore certainly doesn't agree with you. ...
... Forth with optimal hand-coded assembler primitives can evade this cost to a...at the very likely cost of readability/maintainability, as opposed to just taking...it as C and/or assembler primitives? Cheers Dave Well as cache ...had no apparent space reduction. Optimizing primitives will not gain too muh, primitive pair sequences as single words holds more potential. cheers jacko
...This approach-- up-front design work coupled with objective measurement-- is superior to the mindless "I must optimize every primitive" mindset because it focuses on the system. Spending your time optimizing a primitive that takes up a tiny fraction of a system's run-time makes no sense. But you only know...
...This approach-- up-front design work coupled with objective measurement-- is superior to the mindless "I must optimize every primitive" mindset because it focuses on the system. Spending your time optimizing a primitive that takes up a tiny fraction of a system's run-time makes no sense. But you only know ...
... 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? Ideally, if you're going to spend that kind of effort, it... settle on a design. That way your code will clearly and readably reflect a high-performance design, rather than being built for one ...
... compiled languages. An STC-based Forth with optimal hand-coded assembler primitives can evade this cost to a large degree, so I won't be ... 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 ...
..., not the VM. That's a trap that you see endlessly here in comp.lang.forth-- a preoccupation with speed. But not speed of some concrete real-world application, but the speed of some small primitive in the system. You don't see the forrest in the trees. When we argue here, we are quite often concerned about speed. You then step in and say "there's no requirement to be ...
...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? By definition, making your code unreadable and unmaintainable is the ... dozen hand-coded assembly instructions. Note that having a clear, readable and commented code at that point really helps in finding ...
... the VM. That's a trap that you see endlessly here in comp.lang.forth-- a preoccupation with speed. But not speed of some concrete real-world application, but the speed of some small primitive in the system. You don't see the forrest in the trees. When we argue here, we are quite often concerned about speed. You then step in and say "there's no requirement to be performant here". ...
... the speed of some small primitive in the system. The theory,... on speeding up all the primitives, the performance of the overall ... the very likely cost of readability/maintainability, as opposed to just ... as C and/or assembler primitives? The first step is to ... when coding in a more primitive language makes sense. If you'... core routines in a more primitive language makes sense. But before...
