public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/36906] #pragma GNU poison index()
Date: Mon, 11 Aug 2008 00:29:00 -0000	[thread overview]
Message-ID: <20080811002822.10354.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36906-10965@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from pinskia at gcc dot gnu dot org  2008-08-11 00:28 -------
Let me expand on what I mean by the attribute deprecated.
See http://gcc.gnu.org/onlinedocs/gcc-4.3.0/gcc/Function-Attributes.html:

deprecated
The deprecated attribute results in a warning if the function is used anywhere
in the source file. This is useful when identifying functions that are expected
to be removed in a future version of a program. The warning also includes the
location of the declaration of the deprecated function, to enable users to
easily find further information about why the function is deprecated, or what
they should do instead. Note that the warnings only occurs for uses:
          int old_fn () __attribute__ ((deprecated));
          int old_fn ();
          int (*fn_ptr)() = old_fn;

results in a warning on line 3 but not line 2.

The deprecated attribute can also be used for variables and types (see Variable
Attributes, see Type Attributes.) 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36906


  parent reply	other threads:[~2008-08-11  0:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23  6:51 [Bug preprocessor/36906] New: " Dave at Yost dot com
2008-07-23  7:09 ` Andrew Thomas Pinski
2008-07-23  7:10 ` [Bug preprocessor/36906] " pinskia at gmail dot com
2008-08-11  0:29 ` pinskia at gcc dot gnu dot org [this message]
2008-09-02 19:23 ` tromey at gcc dot gnu dot org
2008-12-24 23:16 ` pinskia at gcc dot gnu dot org

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=20080811002822.10354.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).