Re: problem with macro definitions

[Michael Heerdegen <michael_heerdegen@web.de>]

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Your macro `state-eof' actually does find the value at compile time.
> It's still an unusual use case for `defmacro' which is normally code
> transformation.  Your `state-eof' calls just expand to a number.  You
> can do this, but in real life one would probably prefer a different
> solution, like defining this number as a `defconst', depending on the
> actual use case.

BTW, a good method to do calculations at compile time is to use
`eval-when-compile'.  Depending on the actual use case, it's mostly
still good enough and easier to do such things (once) at load time.


Michael.