News for hackers. Stuff that matters.
Re:How to slice your code into continuations by TeMPOraL on Wednesday May 08, 2019 @05:09AM (#19857114)
> a macro preprocessor which had access to the actual character stream can elect to do things not possible in lisp macros—e.g., distinguish on indentation or something to that effect—but also can recover all of the lisp macro techniques by merely parsing the character stream.

Common Lisp has the mechanism called "reader macros" that can do that. It's a separate mechanism, because it works at "read time", which is much earlier than the "macroexpansion time" when the regular macros are processed.

Re:How to slice your code into continuations by tel on Tuesday May 14, 2019 @06:21PM (#19914393)
Yep, "macros" can operate at any point during the compilation/interpretation process to transform the inputs. Generally speaking, the earlier on the more simplistic the structures and the less inferential products available. Also, the greater flexibility and power. Later on, early stages of compilation/interpretation will strip away information, simplify products, add inferential information, etc. These pieces can be made available to macro systems staged later on.

Lisp's most famous macros exist somewhat early in the compilation process, where trees have been parsed but variables aren't interpreted and the data structures are still simple.