lisp宏以程序片段作为输入。这个程序片段被表示为一个数据结构，可以按照您喜欢的任何方式进行操作和转换。最后，宏输出另一个程序片段，这个片段是在运行时执行的。

c#没有宏功能，但是如果编译器将代码解析为CodeDOM树，并将其传递给一个方法，该方法将其转换为另一个CodeDOM，然后将其编译为IL，则会有等效的宏功能。

这可以用来实现“糖”语法，如for each-statement using-clause, linq select-expressions等等，作为转换为底层代码的宏。

如果Java有宏，您就可以在Java中实现Linq语法，而不需要Sun更改基本语言。

下面是在c#中实现lisp风格的宏的伪代码:

define macro "using":
    using ($type $varname = $expression) $block
into:
    $type $varname;
    try {
       $varname = $expression;
       $block;
    } finally {
       $varname.Dispose();
    }

lisp宏以程序片段作为输入。这个程序片段被表示为一个数据结构，可以按照您喜欢的任何方式进行操作和转换。最后，宏输出另一个程序片段，这个片段是在运行时执行的。

c#没有宏功能，但是如果编译器将代码解析为CodeDOM树，并将其传递给一个方法，该方法将其转换为另一个CodeDOM，然后将其编译为IL，则会有等效的宏功能。

这可以用来实现“糖”语法，如for each-statement using-clause, linq select-expressions等等，作为转换为底层代码的宏。

如果Java有宏，您就可以在Java中实现Linq语法，而不需要Sun更改基本语言。

下面是在c#中实现lisp风格的宏的伪代码:

define macro "using":
    using ($type $varname = $expression) $block
into:
    $type $varname;
    try {
       $varname = $expression;
       $block;
    } finally {
       $varname.Dispose();
    }

通用Lisp宏本质上扩展了代码的“语法原语”。

例如，在C语言中，switch/case结构只适用于整型，如果你想将它用于浮点数或字符串，你就只能使用嵌套的if语句和显式比较。你也不可能编写一个C宏来为你做这项工作。

但是，由于lisp宏(本质上)是一个lisp程序，它接受代码片段作为输入，并返回代码来替换宏的“调用”，因此您可以尽可能地扩展您的“原语”库，通常最终会得到一个更可读的程序。

要在C中做同样的事情，您必须编写一个自定义预处理器，它会吃掉您的初始(不完全是C)源代码，并吐出C编译器可以理解的东西。这不是一种错误的方法，但它不一定是最简单的。

In python you have decorators, you basically have a function that takes another function as input. You can do what ever you want: call the function, do something else, wrap the function call in a resource acquire release, etc. but you don't get to peek inside that function. Say we wanted to make it more powerful, say your decorator received the code of the function as a list then you could not only execute the function as is but you can now execute parts of it, reorder lines of the function etc.

While the above all explains what macros are and even have cool examples, I think the key difference between a macro and a normal function is that LISP evaluates all the parameters first before calling the function. With a macro it's the reverse, LISP passes the parameters unevaluated to the macro. For example, if you pass (+ 1 2) to a function, the function will receive the value 3. If you pass this to a macro, it will receive a List( + 1 2). This can be used to do all kinds of incredibly useful stuff.

Adding a new control structure, e.g. loop or the deconstruction of a list Measure the time it takes to execute a function passed in. With a function the parameter would be evaluated before control is passed to the function. With the macro, you can splice your code between the start and stop of your stopwatch. The below has the exact same code in a macro and a function and the output is very different. Note: This is a contrived example and the implementation was chosen so that it is identical to better highlight the difference. (defmacro working-timer (b) (let ( (start (get-universal-time)) (result (eval b))) ;; not splicing here to keep stuff simple ((- (get-universal-time) start)))) (defun my-broken-timer (b) (let ( (start (get-universal-time)) (result (eval b))) ;; doesn't even need eval ((- (get-universal-time) start)))) (working-timer (sleep 10)) => 10 (broken-timer (sleep 10)) => 0

我认为我从来没有见过比这个家伙解释得更好的Lisp宏:http://www.defmacro.org/ramblings/lisp.html