Hygienic macro expansion

Kohlbecker, Eugene E.; Friedman, Daniel P.; Felleisen, Matthias; Duba, Bruce F.

doi:10.1145/319838.319859

Cited by 196 publications

(109 citation statements)

References 1 publication

Supporting

Mentioning

107

Contrasting

Order By: Relevance

“…In the functional-languages community, a wide-spread technique for ensuring that macros respect scoping rules is hygiene. Kohlbecker et al introduce hygienic expansion [13]. Clinger and Rees present an improved algorithm for renaming identifiers to guarantee hygiene [5].…”

Section: Language-specific Safe Macro Systemsmentioning

confidence: 99%

“…(1) Some macro systems are well encapsulated from the compiler or interpreter but are unsafe, e.g., the C preprocessor executes before the target-language compiler, but may generate erroneous code. (2) Some macro systems are safe but are tightly integrated with the target languages, e.g., the Scheme interpreter hygienically implements the core language together with its macro system [13,5].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Marco: Safe, Expressive Macros for Any Language

Lee

Grimm

Hirzel

et al. 2012

ECOOP 2012 – Object-Oriented Programming

View full text Add to dashboard Cite

Abstract. Macros improve expressiveness, concision, abstraction, and language interoperability without changing the programming language itself. They are indispensable for building increasingly prevalent multilingual applications. Unfortunately, existing macro systems are wellencapsulated but unsafe (e.g., the C preprocessor) or are safe but tightlyintegrated with the language implementation (e.g., Scheme macros). This paper introduces Marco, the first macro system that seeks both encapsulation and safety. Marco is based on the observation that the macro system need not know all the syntactic and semantic rules of the target language but must only directly enforce some rules, such as variable name binding. Using this observation, Marco off-loads most rule checking to unmodified target-language compilers and interpreters and thus becomes language-scalable. We describe the Marco language, its languageindependent safety analysis, and how it uses two example target-language analysis plug-ins, one for C++ and one for SQL. This approach opens the door to safe and expressive macros for any language.

show abstract

Section: Language-specific Safe Macro Systemsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Marco: Safe, Expressive Macros for Any Language

Lee

Grimm

Hirzel

et al. 2012

ECOOP 2012 – Object-Oriented Programming

View full text Add to dashboard Cite

show abstract

“…Dynamic variables in Emacs LISP and Common LISP are a good example of a violation of scope safety [30,24]. Scheme R5RS's macro language is designed to be scope safe [21].…”

Section: Variables In Meta-programmingmentioning

confidence: 99%

Directly reflective meta-programming

Stump

2008

Higher-Order Symb Comput

View full text Add to dashboard Cite

Existing meta-programming languages operate on encodings of programs as data. This paper presents a new meta-programming language, based on an untyped lambda calculus, in which structurally reflective programming is supported directly, without any encoding. The language features call-by-value and call-by-name lambda abstractions, as well as novel reflective features enabling the intensional manipulation of arbitrary program terms. The language is scope safe, in the sense that variables can neither be captured nor escape their scopes. The expressiveness of the language is demonstrated by showing how to implement quotation and evaluation operations, as proposed by Wand. The language's utility for meta-programming is further demonstrated through additional representative examples. A prototype implementation is described and evaluated.

show abstract

“…Second, it can benefit greatly from primitives such as those provided by xslt. xt3d also suggests shortcomings in and improvements to xml, such as information to create hygienic [12] transformers. We expect such work will expose ideas from functional and declarative languages to much broader audiences.…”

Section: Summary and Future Workmentioning

confidence: 99%

Transformation-by-Example for XML

Krishnamurthi

Gray

Graunke³

1999

Practical Aspects of Declarative Languages

View full text Add to dashboard Cite

Abstract. xml is a language for describing markup languages for structured data. A growing number of applications that process xml documents are transformers, i.e., programs that convert documents between xml languages. Unfortunately, the current proposals for transformers are complex general-purpose languages, which will be unappealing as the xml user base broadens and thus decreases in technical sophistication. We have designed and implemented xt3d, a highly declarative xml specification language. It demands little more from users than a knowledge of the expected input and desired output. We illustrate the power of xt3d with several examples, including one reminiscent of polytypic programming that greatly simplifies the import of xml values into general-purpose languages.

show abstract

Hygienic macro expansion

Cited by 196 publications

References 1 publication

Marco: Safe, Expressive Macros for Any Language

Marco: Safe, Expressive Macros for Any Language

Directly reflective meta-programming

Transformation-by-Example for XML

Contact Info

Product

Resources

About