Flyer

Ow! Now we are entering the taboo area of state-smartness… In noForth we have the word FLYER . It handles state-smartness in a uniform way. FLYER uses DIVE and both are implementation dependent FLYER is a NOOP during compile time. This is what FLYER does when STATE=0 :

forth goes in compile mode and compiles until end of definition
then the compiled code is executed
forth leaves compile mode and forgets the compiled code

<HTML><ul></HTML> <HTML><li></HTML><HTML></HTML>In definitions<HTML></HTML>

: ." ( a n -- ) flyer ." ;

<HTML></HTML>This new .„ is state-smart<HTML></HTML><HTML></li></HTML> <HTML><li></HTML><HTML></HTML>Outside of definitions we need -FLY<HTML></HTML>

: -FLY 2r> r> 2>r >r ; immediate ( r: x y z -- z x y )

<HTML></HTML>Use of conditionals is possible between FLYER and -FLY<HTML></HTML>

8 0  flyer  do i . loop   -fly

(an)