Re:Writing a Self-Mutating x86_64 C Program (2013)
by lispm on Tuesday January 15, 2019 @03:04AM
(#18909497)
If macros are running at compile time, then we don't think that this particular code is self modifying.
If we run code in a Lisp interpreter, then one can write self-modifying code. It's possible to get visible effects. It's also possible to use it during debugging code.
Re:Writing a Self-Mutating x86_64 C Program (2013)
by kazinator on Tuesday January 15, 2019 @03:25AM
(#18909588)
Regardless of any lack of referential hygiene, or reliance on side-effects such that the same piece of code is not expanded the same way twice, CL macros must not mutate the input AST, period. It is undefined behavior, and easily avoidable.
Doesn't mean I suggest doing this, but please do not sell unhygenic CL macros short. :) In fact, in CL one has to go to some lengths to be careful to make macro outputs "safe."