words mustn't be added by instant resolving during suspended compilation about yoda

[Bushmills]

Actually, it may be possible to allow nested compiles. Will check.
It seems that the hardest part is what is also reponsable for
issue 3 - once that is solved as thought of there, nested compiles might be not too hard to add.
Reason for why that could work is that then compilation would not even have started when [ ] is encountered - but currently, header is already created (which the envisioned solution for issue 3 would change)

[Bushmills]

nested compiles are harder than first thought. The idea has been dropped for now. But since late headers have been introduced, detecting whether an attempt to compile yet unresolved words during suspended compilation is much simpler now. Therefore it may be safe to let satisfy detect that condition, and decline compilation (or let satisfy simply execute need for resolving at a more appropriate time, later - but probably does throwing a "word not found" error for those not yet existing words make more sense).

[Bushmills]

condition "suspended compilation" is caught, satisfy won't compile code of yet unresolved words when those are referenced between [ ]. Nor is a forward reference created. If you want to execute a forward referenced word between [ ], use satisfy before starting compiling a word.