Jeremy Penner 2f59db6766 Implement string constants, buffers, macro barriers ... macro barriers are a hack to say "this form does its own macroexpansion internally" so that we can have state-smart macros that expand to different values depending on if they are being used in code or in a function definition. This seems like a real bad design choice but I can't think of a better one right now! (not quite true: the better design choice is to allow forms to return opgens, and then define a :bytes form that returns the address of the generated thing. :bytes could be understood by :buffer directly. But that's... complicated.)		2021-09-26 23:07:36 -04:00
..
bootstub.fnl	refactor set!, byte-at, word-at, long-at	2021-09-26 00:34:48 -04:00
graphics.fnl	Implement macros, symbol expansion (replaces constants, getters)	2021-09-26 20:32:17 -04:00
toolbox.fnl	Implement macros, symbol expansion (replaces constants, getters)	2021-09-26 20:32:17 -04:00
u2-debug.fnl	Implement string constants, buffers, macro barriers	2021-09-26 23:07:36 -04:00
uthernet2.fnl	refactor set!, byte-at, word-at, long-at	2021-09-26 00:34:48 -04:00