RFA: test macro scoping

[Jim Blandy]

I've committed this patch, with changes for the recent `show macro' ->
`info macro' renaming.

As mentioned below, it introduces 23 new known failures (gdb/555).

Jim Blandy <jimb@redhat.com> writes:

> Here is a revision of this patch, using names based on `macscp'
> instead of `macros'.  `macros' was supposed to stand for `macro
> scoping', but it really just looks like the plural of `macro'.  I'm
> planning to post patches for macro expansion (`macexp') and macro
> commands (`maccmd'), so the name `macscp' fits better.
> 
> There are no other differences between this patch and its predecessor.
> 
> Jim Blandy <jimb@redhat.com> writes:
> 
> > This test only checks GDB's ability to figure out which macros are in
> > scope where.  (`macros' is supposed to be an abbreviation for `macro
> > scope'; should I rename these to `macrosc<mumble>?'  I need a spot for
> > the file number...)
> > 
> > This introduces about 23 new failures.  They reflect a genuine bug,
> > but one that will take a lot of work to fix.  If I understand the
> > conventions correctly, such bugs are supposed to be marked with
> > "setup_kfail", with a reference to a GDB PR describing the bug,
> > commented out.  So I've filed gdb/555, and marked the failing tests
> > attributable to that bug accordingly.  If this isn't right, please set
> > me straight.
> > 
> > More tests will be forthcoming for the macro commands and macro
> > expansion.
> > 
> > 2002-05-21  Jim Blandy  <jimb@redhat.com>
> > 
> > 	* macros.exp, macros1.c, macros2.h, macros3.h, macros4.h: New
> > 	tests.