en:pfw:flyer
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| en:pfw:flyer [2023-09-04 18:14] – gelöscht - Externe Bearbeitung (Unbekanntes Datum) 127.0.0.1 | en:pfw:flyer [2023-09-04 18:14] (current) – ↷ Seite von pfw:flyer nach en:pfw:flyer verschoben uho | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== 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 | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | : ." ( a n -- ) flyer ." ; | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | : -FLY 2r> r> 2>r >r ; immediate ( r: x y z -- z x y ) | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | < | ||
| + | 8 0 flyer do i . loop -fly | ||
| + | </ | ||
| + | < | ||
| + | |||
| + | (an) | ||