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



------- Comment #1 from pinskia at gmail dot com  2008-07-23 07:09 -------
Subject: Re:   New: #pragma GNU poison index()

Try the attribute deprecated.

Sent from my iPhone

On Jul 22, 2008, at 23:50, "Dave at Yost dot com" <gcc-bugzilla@gcc.gnu.org 
 > wrote:

> There should be a way to poison a symbol only when it is used as a  
> function or
> macro call. I suggest that following a symbol with a pair of  
> parentheses might
> be a serviceable syntax for this. With this feature, the symbol  
> rindex would
> still be usable for variables.
>
>
> -- 
>           Summary: #pragma GNU poison index()
>           Product: gcc
>           Version: unknown
>            Status: UNCONFIRMED
>          Severity: enhancement
>          Priority: P3
>         Component: preprocessor
>        AssignedTo: unassigned at gcc dot gnu dot org
>        ReportedBy: Dave at Yost dot com
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36906
>


-- 


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


  parent reply	other threads:[~2008-07-23  7:10 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 ` pinskia at gmail dot com [this message]
2008-08-11  0:29 ` [Bug preprocessor/36906] " pinskia at gcc dot gnu dot org
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=20080723070922.5629.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).