As a motivating example, consider the (somewhat haphazard) architecture of the current MacroParse compiler. You can think of it as a de-multiplexer that directs and delegates different portions of the input to different sub-language subsystems:
the Mini-Scan regex parser (because I'd really rather only have one)
a language of (macro-expanded) context-free production rules
the "literate" embedding of a language definition into a mark-down document
crufty hand-rolled ad-hackery at the boundaries of these
The object of this issue is to explore and resolve ways to refer to one language inside the definition of another without having to repeat definitions (for different applications) or worry about namespace conflicts.
As a motivating example, consider the (somewhat haphazard) architecture of the current MacroParse compiler. You can think of it as a de-multiplexer that directs and delegates different portions of the input to different sub-language subsystems:
The object of this issue is to explore and resolve ways to refer to one language inside the definition of another without having to repeat definitions (for different applications) or worry about namespace conflicts.