From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10601 invoked by alias); 21 Aug 2002 17:09:43 -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 10593 invoked from network); 21 Aug 2002 17:09:41 -0000 Received: from unknown (HELO gash2.peakpeak.com) (207.174.178.17) by sources.redhat.com with SMTP; 21 Aug 2002 17:09:41 -0000 Received: from fleche.redhat.com (tq0164.peakpeak.com [207.174.177.164]) by gash2.peakpeak.com (8.9.3/8.9.3) with ESMTP id LAA31642; Wed, 21 Aug 2002 11:09:39 -0600 Received: by fleche.redhat.com (Postfix, from userid 1000) id B2A754F8099; Wed, 21 Aug 2002 11:08:53 -0600 (MDT) To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: Issue an internal warning on first deprecated function call References: <3D5C248D.4030003@ges.redhat.com> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom X-Zippy: Oh, FISH sticks, CHEEZ WHIZ, GIN fizz, SHOW BIZ!! Date: Wed, 21 Aug 2002 10:09:00 -0000 In-Reply-To: <3D5C248D.4030003@ges.redhat.com> Message-ID: <87bs7wm95m.fsf@fleche.redhat.com> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-08/txt/msg00249.txt.bz2 >>>>> "Andrew" == Andrew Cagney writes: Andrew> The idea is to issue an internal-warning on the first call to a Andrew> deprecated [multi-arch] function. Andrew> Thoughts? Variations on the idea? What about marking functions as deprecated at compile time using __attribute__? Then the burden falls on the maintainers not to call deprecated functions. (I'm not certain that __attribute__((deprecated)) works if you are calling through a function pointer.) Tom