Fri Mar 23 21:16:39 EDT 2007
i'm running into problems with macro generating code.. fixed
some. cleaned up some in vm.ss
now i have an interesting problem with delayed eval: macro defs (side
effects) get delayed till after the macros are used..
ok i think i got it..
what about tagging names that are supposed to be cat semantics in a
ok.. this concludes a long run. from the top of my head, things are
better now because:
- badnop is better defined as a forth compiler with fixed
functionality mentioned above
- code makes clear indication if functions are used as cat semantics
== code that compiles something into a stack primitive.
- 'compile' and 'literal' are now CAT macros
- the state monad uses a more highlevel wrapper
things to do still:
- constants for disassembler
- core restart
- clean up source file layout, maybe split in more modules + docu
funny... running into an evaluation order problem again.. maybe i
should use some kind of module / scheme namespace trick to get rid of
this? because load/eval/parse order is kind of arbitrary now.. ->
nothing to worry about. it was a stupid typo.
got the meta-patterns macro working too. this is actually an
interesting idiom: just wrap a single macro around a body of 'define'
statements to alter the way they are used: it allows proper syntax
hilighting + individual testing.