-
Notifications
You must be signed in to change notification settings - Fork 0
macros
There is now some very basic macro-like support implemented in the lambda conversion step (where we go from the abstract syntax tree to a lambda representation). It isn't a true macro facility, in fact what I'm calling "macros" are really just lazy functions. For example in the preamble we now have:
macro AND(a, b) { if (a) { b } else { false } }
infix left 30 "and" AND;
And similarly for the other logical operators. Note this preserves
the short circuiting of the and
, e.g.
let
fn a() { print "a called"; false }
fn b() { print "b called"; true }
fn c() { print "c called"; true }
in
a() and b() or c();
prints:
a called
c called
How this works is, the macro is parsed and converted to a function
and a note made in the compile-time environment that it is a
macro. Then if it is invoked later, each of it's arguments
is wrapped in a thunk before passing them to the function.
Likewise within the macro body, any reference to a formal argument
a
is replaced with a call to that argument a()
. To return to the AND
example from above
macro AND(a, b) { if (a) { b } else { false } }
is rewritten to
fn AND(a, b) { if (a()) { b() } else { false } }
and likewise any call to AND(a(), b())
becomes AND(fn () {a()}, fn () {b()})
which a subsequent
generic optimization step will transform to AND(a, b)
, because fn () { a () }
can be
reduced to just a
. In summary
AND(a(), b()) => if (a()) { b() } else { false }
Which is just what is required.
CEKF(s) a.k.a. F Natural a.k.a F♮