Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: tromey@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: Issue an internal warning on first deprecated function call
Date: Mon, 09 Sep 2002 11:10:00 -0000	[thread overview]
Message-ID: <3D7CE3F5.9060100@ges.redhat.com> (raw)
In-Reply-To: <87bs7wm95m.fsf@fleche.redhat.com>

>>>>>> "Andrew" == Andrew Cagney <ac131313@ges.redhat.com> 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.)

Hmm, thanks.  I thought there was such an attribute but couldn't find it 
in the version of the doco I was looking at.  I'll try to check it out.

thanks,
Andrew



      reply	other threads:[~2002-09-09 18:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-15 15:01 Andrew Cagney
2002-08-15 15:33 ` Kevin Buettner
2002-08-15 18:14   ` Daniel Jacobowitz
2002-08-15 18:36     ` Andrew Cagney
2002-08-16  6:31   ` Carlos O'Donell
2002-08-16  6:50     ` Andrew Cagney
2002-08-16  7:09       ` Carlos O'Donell
2002-08-16  7:16         ` Andrew Cagney
2002-08-18 11:35       ` Eli Zaretskii
2002-08-19 18:23         ` Andrew Cagney
2002-08-20  6:19           ` Carlos O'Donell
2002-08-20 23:36             ` Eli Zaretskii
2002-08-21  6:07               ` Carlos O'Donell
2002-08-21  8:21                 ` Andrew Cagney
2002-08-21  8:52                   ` Kevin Buettner
2002-08-21  9:29                     ` Andrew Cagney
2002-08-22  0:49                 ` Eli Zaretskii
2002-08-22  5:43                   ` Carlos O'Donell
2002-08-21 10:09 ` Tom Tromey
2002-09-09 11:10   ` Andrew Cagney [this message]

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=3D7CE3F5.9060100@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=tromey@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