No, interpreted code inside some other program is something I would definitely class as scripting -- spreadsheet macros, and practically anything else done with VB. I would not consider them macros -- that's an abuse of terminology.
A proper macro is a higher-order function: it returns source code that is then compiled, interpreted, or assembled; in other words, it gets run at compile time. E.g. assembly-language macros, Lisp macros, C macros -- I don't know C# so I don't know whether it has something similar. Reasonably pure macro languages include M4 and TeX (LaTeX is a set of TeX macros); Emacs was originally a collection of TECO macros.
Lisp macros are cool because, unlike all the other examples up there, the arguments of the function are lists rather than strings.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2018-07-27 08:26 pm (UTC)A proper macro is a higher-order function: it returns source code that is then compiled, interpreted, or assembled; in other words, it gets run at compile time. E.g. assembly-language macros, Lisp macros, C macros -- I don't know C# so I don't know whether it has something similar. Reasonably pure macro languages include M4 and TeX (LaTeX is a set of TeX macros); Emacs was originally a collection of TECO macros.
Lisp macros are cool because, unlike all the other examples up there, the arguments of the function are lists rather than strings.