From: Ian Lance Taylor <ian@airs.com>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: <drow@false.org>, <binutils@sources.redhat.com>,
<gdb@sources.redhat.com>
Subject: Re: gas: should duplicate .macro directives be allowed?
Date: Mon, 07 Mar 2005 16:15:00 -0000 [thread overview]
Message-ID: <m3fyz7l9fd.fsf@gossamer.airs.com> (raw)
In-Reply-To: <s22c045e.046@emea1-mh.id2.novell.com>
"Jan Beulich" <JBeulich@novell.com> writes:
> Yes, the change was deliberate, and I don't think it'd be wise to revert
> it (it's simply dangerous considering that you might have these
> collisions resulting from two include files, each of which relies on
> their definition of the respective macro). Instead, if you need to
> override a previous macro definition (and know what you're doing), you
> can use easily use .purgem before the new definition (really, I'd rather
> recommend not to to catch the collision). Jan
That seems more or less reasonable to me, but Daniel is correct that
this change must be mentioned in NEWS. It should be documented
somewhere in as.texinfo as well, if it is not already.
Ian
next prev parent reply other threads:[~2005-03-07 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 7:36 Jan Beulich
2005-03-07 16:15 ` Ian Lance Taylor [this message]
2005-03-07 16:20 ` Daniel Jacobowitz
2005-03-08 1:02 ` Erik Christiansen
-- strict thread matches above, loose matches on Subject: below --
2005-03-06 17:56 Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3fyz7l9fd.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=JBeulich@novell.com \
--cc=binutils@sources.redhat.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox