Re: [gforth] A little do-nothing in recognizer.fs: get-stack

[James Gere]

     Now perplexed.  "see get-stack" gives:

:   get-stack
     noop   swap   @   noop   >r  cells   bounds   swap
     ?do     i   @   noop   <cell>
     -loop
     r>   ;

.  recognizer.fs source gives:

: get-stack ( rec-addr -- xt1 .. xtn n )
    dup swap @ dup >r cells bounds swap ?DO
I @
    cell -LOOP  r> ;

.  I realize "see" can't always keep up with "c,"  and recognize
that the cached tos needn't be dup'ed, but where does the last noop come
from?  (They all optimize out.)
     Is the "nonce" swap,  in the source, there to trigger this behavior, or just
an oversight?