This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: macro behavior
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Jan Beulich <JBeulich at novell dot com>
- Cc: binutils at sources dot redhat dot com
- Date: Wed, 20 Apr 2005 05:34:30 -0400 (EDT)
- Subject: Re: macro behavior
- References: <s2662ccc.060@emea1-mh.id2.novell.com>
On Wed, 20 Apr 2005, Jan Beulich wrote:
> .macro gproc name:req, more:vararg
> .global \name
> .type \name, @proc
> .ifnb \more
> gproc \more
> .endif
> .endm
>
> These qualifiers mean
>
> req argument value required
> vararg parameter covers all remaining arguments, if any
>
> while by default specifying an argument value would remain
> optional (including the use of =<value> to specify a default
> value). Of course, the use of : here again may present some
> issues, since MMIX allows : in symbol names, but other than
> above I think this could be tolerated, just requiring to use
> white space around the colon to disambiguate things.
Whitespace separates parameters, not just comma, so I don't
think that'd be disambiguating. I stand by my position that
allowing other than alphanumerics + _ in macro parameter names
is a walk down the wrong lane. The powerpc symbol issue seems
to support that position.
(BTW, I agree with davem that your overlong lines makes
communication harder.)
brgds, H-P