Re: RFA: Switch TYPE_CODE_METHOD to store arguments like TYPE_CODE_FUNCTION

[Jim Blandy <jimb at redhat dot com>]

Minor observation:

In gdbtypes.h, your patch makes the following change to `struct field':

     /* Name of field, value or argument.
-       NULL for range bounds and array domains.  */
+       NULL for range bounds, array domains, and member function
+       arguments.  */
 
     char *name;

Is there any reason this *must* be null?  Aren't there times where we
do know a method's arguments' names, and where we could fill this in?

I guess I'm thinking about the way prototyped function types in C may
or may not include the names:

        typedef int (*foo_t) (int x, int y);
        typedef int (*bar_t) (int, int);
        typedef int (*baz_t) (int x, int);

Is there any analog to this in C++?