point of order: how should I post the macro patch?

[Jim Blandy <jimb at redhat dot com>]

I'm not sure how people would like to see this patch presented.  If
you want to see the smallest patch that actually affects GDB's
behavior, well, that'd be the macro table module, the macro expander
module, the macro commands module, the changes to dwarf2read.c to fill
in the macro table module, and the changes spread around throughout
GDB to add the macro table to the existing symbol table structures.
It's pretty big, but you get the "macro expand", "show macro",
etc. commands.  Actually making the C expression evaluator do macro
expansion would be a final, separate patch.

Or, if you'd rather have the patch broken up into more digestible
pieces that individually have no effect, then I can post the pieces in
the following order:
- the macro table module
- the changes throughout GDB to add the macro table to the existing
  symbol table structures (but at this point the table is never used)
- the changes to dwarf2read.c to actually fill in the table
- the macro expander module
- the macro commands module, to give you "show macro" and "macro
  expand",
- the C evaluator changes

Whatever folks want to see, I'm happy to do.  If you don't care, I'm
going to do the former: post it as two big patches.