From: do-not-use@swldwa.uk   
      
   On 12/08/2024 10:45, albert@spenarnc.xs4all.nl wrote:   
   > In article,   
   > Gerry Jackson  wrote:   
   >> ISTM that using the data stack to hold the control stack is an   
   >> anachronism that was used in early Forth systems because of the limited   
   >> amount of memory available. I also think that the system should not get   
   >> in the way of user programs as putting control stack data on the data   
   >> stack certainly does.   
   > It alleviates restriction. Marcel Hendrix hated the restrictions of   
   > R> >R and added the socalled "system stack" S> >S that can be used   
   > over definitions. The disadvantage is of course that there are more   
   > regions of memory that you have to keep track of.   
   > I think that added complexity is a more important consideration as   
   > memory usage. The more stacks you have and the more stack items   
   > you keep in registers, the more difficult e.g. task switching becomes.   
      
   As use of a control stack is during compilation, speed is not too   
   important so why would register(s) be used for it?   
      
   --   
   Gerry   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)