From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Monnier Subject: Re: Why does evaluating a piece of Elisp code seemingly not expand a macro? Date: Mon, 18 Jan 2016 15:19:36 -0500 Message-ID: References: <87a8o7duj6.fsf@mbork.pl> <878u3rcdpu.fsf@gmail.com> <87io2r95n2.fsf@mbork.pl> <8737tu8xka.fsf@mbork.pl> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <8737tu8xka.fsf@mbork.pl> (Marcin Borkowski's message of "Mon, 18 Jan 2016 21:03:33 +0100") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org To: Marcin Borkowski Cc: help-gnu-emacs@gnu.org, emacs-orgmode@gnu.org List-Id: emacs-orgmode.gnu.org > Does that mean that it's possible that a function definition contains > unexpanded macros? Yes. > Does that mean that `symbol-function' will expand them? AFAIK it currently never happens there, but if your code relies on this property it's probably got a bug. > Does that mean that if I define a macro, then a function using that > macro, and then change the definition of the macro, the behavior of the > function is undefined? Yes. Stefan