Re: Avoid treating the stack as an array [Re: "Back & Forth" is back!]

dxf <dxforth@gmail.com> writes:

Compiling under DX-Forth resulted in a code size of 23 and 26 bytes
respectively.  Under VFX ...

I can't help it if those compilers generate worse code for the locals
version.  Can you conveniently try lxf?

Not only were you able to read forth code, the result was more
efficient.

Sometimes it isn't too hard to read, sometimes it takes head scratching,
and sometimes I can't make any sense of it.  The function Anton posted
was an example that didn't make sense.  I remember thinking I might sit
down and try to figure it out to rewrite it, but it doesn't seem worth
the effort.

Anyway, if efficiency was important for that example, I'd use CODE.