This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Re: .macro behavior


>>> Hans-Peter Nilsson <hp@bitrange.com> 08.02.05 18:31:37 >>>
>On Tue, 8 Feb 2005, Jan Beulich wrote:
>
>> >> >> only allows [[:alpha:]_$][[:alnum:]_$]*
>> >
>> >I think this restriction is actually good.  Calls for the least
>> >amount of surprises when applying the same macro to different
>> >GAS ports.
>>
>> Not so. If, on IA-64 as an example, I want to define an
>> instruction-like macro, I need to have '.' as an acceptable
character
>> for the macro name.
>
>I thought you were talking about macro *parameter names*, as
>that's the change that exposed the mistake in the MMIX
>test-case.  I agree the macro names themselves should be
>freely chosen (anything but whitespace or whatever).

I'm actualy talking about both, and since both are symbol names, both
should get the same treatment as ordinary symbols (despite agreeing that
for macro parameters the previous restriction is less hurting).
Otherwise it's just inconsistent.

Jan


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]