From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21861 invoked by alias); 7 Mar 2005 16:20:20 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 21416 invoked from network); 7 Mar 2005 16:19:21 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 7 Mar 2005 16:19:21 -0000 Received: from drow by nevyn.them.org with local (Exim 4.44 #1 (Debian)) id 1D8Kwv-0002VC-D5; Mon, 07 Mar 2005 11:19:17 -0500 Date: Mon, 07 Mar 2005 16:20:00 -0000 From: Daniel Jacobowitz To: binutils@sources.redhat.com, gdb@sources.redhat.com Cc: JBeulich@novell.com Subject: Re: gas: should duplicate .macro directives be allowed? Message-ID: <20050307161917.GA9583@nevyn.them.org> Mail-Followup-To: binutils@sources.redhat.com, gdb@sources.redhat.com, JBeulich@novell.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040907i X-SW-Source: 2005-03/txt/msg00073.txt.bz2 On Mon, Mar 07, 2005 at 11:15:02AM -0500, Ian Lance Taylor wrote: > "Jan Beulich" 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. While I'm wishing, it would be nice if the documentation mentioned .purgem somewhere from .macro. I spent a while trying to figure out if there was a right way to do this from the manual, and did not come across .purgem until Jan mentioned it. -- Daniel Jacobowitz CodeSourcery, LLC