miniblog.

I've just added closure support to my toy programming language: https://github.com/Wilfred/garden/commit/d1fb4566a2187dfe98fb1d2278a7a0d2acd8059e Closures are more fiddly than I expected, but I now have a much better understanding of what downward/upward funargs are :) (Downward: passing a closure, upward: returning a closure)

Today I learnt that gcc can mean 'Google Closure Compiler'. It's a sophisticated compiler, but I suppose its use cases are sufficiently non-overlapping with C compilers to avoid confusion. Surprised me though.

I was slightly shocked when a Common Lisper first pointed out to me that macros are syntactic. For example, threading macros aren't limited to function composition. (->> "UTC" (current-time-string (current-time)) (lambda ())) This elisp is building a closure!