Forth like interpreter

[Darrell]

Samuel A. Falvo II wrote:
> .....
> __exit__:
> MOV ESI,[EBP]
> ADD EBP,4
> MOV EAX,[ESI]
> ADD ESI,4
> JMP EAX
>
> And there you have it.

Looks like you know a thing or two about this stuff.
Would have thought subroutine threading was faster. I'll have to visit
comp.lang.forth.

> Also, implementing continuations in a language like Forth would be a
living
> hell so severe that Satan wouldn't want to approach it.  The reason is
that
> continuations require the use of garbage collection.

Could I say that your a Forth purist?
I use Forth to describe the family of TIL's that can evolve quickly because
they are expressed as a single strand of RNA. Maybe I need another term for
them.

Forth's dictionary being a singly linked list of variable sized arrays
packed end to end does seem like a garbage collection problem. I've made a
TIL dictionary a hash table and added reference counting in the past. But as
you've said that wouldn't be Forth. And I'll use that as my defense when
someone slams me for talking too much Forth in the Python group.

--Darrell