[PATCH] Re: .macro behavior

[Jan Beulich]

>I don't see what's wrong with that.  I'd say it actually
>simplifies macro definitions and usage.  The macro parameter
>name is used only in a macro definition, as a placeholder. It's
>no big limitation to make it alphanumeric_ only.  Otherwise, the
>macro writer that wants to cater to multiple GAS ports (say, in
>a package similar to glibc) would have to avoid making the
>parameter name followed by any non-space character at all, in
>case some port has that character as part of an identifier.

The change doesn't prevent anyone from continuing to only use
alphanumeric characters for macro parameter names. And such a name can
validly only be followed by a comma or equal sign (perhaps whitespace,
but no other punctuation), so allowing more characters for use in
parameter names can't break anything (at least no properly written
code), unless a port allows '=' in symbol names (those, the existence of
which I question, would have to separate parameter name and = by
whitespace).

Jan