kt97679

Here is the new rot definition: https://github.com/kt97679/forth-dev/commit/2a3b456d1cf536a8ac2b901488b01261cc8e25f3#diff-6e5f6da6018a5fcb663d9b6fdbe51567e1bfb78e4cb8827663465886e0ac9547R120 You can check other commits to see how I replaced low level opcodes with high level definitions. On Sun, Dec 27, 2020 at...

Yes, location 0 holds stack pointer, location 4 holds return stack pointer, locations after that are "registers" to manipulate stack values. On Sun, Dec 27, 2020 at 4:05 PM Mitra...

@monsonite yes, I mentioned in the very beginning that there is not much practical use in the reducing of the number of primitives. This is more of the theoretical question...

@jacereda yes, I'm aware of the OISC, but I'm specifically interested in forth primitives that can be used to define the rest of the system. It is absolutely possible to...

Hi folks, I would like to clarify that my original research was about discovering an orthogonal minimal set of words sufficient for building the whole forth system. Alan Kay once...

I'm afraid 1 word will not work. Memory modification can't be used to implement arithmetic operations. On Wed, Jan 19, 2022 at 7:39 PM Jack J. Woehr ***@***.***> wrote: >...

I really like that when using "issues" I'm getting all updates via email. Will it work the same way with "discussions"?

Ok, posted a test message. I have the same concern as @alexshpilkin : if discussions will work better (btw do we have criteria for "better"?) we will need to do...

@larsbrinkhoff so true :). I generally agree with @massung . Let's try to use "discussions". If folks will be unhappy for some reason we always can fallback to "issues" which...

@patsevanton I encountered the same issue and curious if you found any fix or workaround?