public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/16370] __attribute__((deprecated)) not useful on classes, and ugly function name listed for deperecation warnings on constructor
Date: Sun, 01 May 2005 05:21:00 -0000	[thread overview]
Message-ID: <20050501052141.23139.qmail@sourceware.org> (raw)
In-Reply-To: <20040705134454.16370.tim.vanholder@anubex.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]


------- Additional Comments From gdr at integrable-solutions dot net  2005-05-01 05:21 -------
Subject: Re:  __attribute__((deprecated)) not useful on classes, and ugly function name listed for deperecation warnings on constructor

"pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:

| ------- Additional Comments From pinskia at gcc dot gnu dot org  2005-05-01 03:41 -------
| We now get:
| t.cc:36: warning: ‘__comp_ctor ’ is deprecated (declared at t.cc:18)
| 
| note the extra space.

The extra space is part of the name, if you ask me.

-- Gaby


-- 


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


  parent reply	other threads:[~2005-05-01  5:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-05 13:44 [Bug c++/16370] New: " tim dot vanholder at anubex dot com
2004-08-02  1:14 ` [Bug c++/16370] " pinskia at gcc dot gnu dot org
2004-11-01  0:28 ` pinskia at gcc dot gnu dot org
2005-05-01  3:41 ` pinskia at gcc dot gnu dot org
2005-05-01  5:21   ` Gabriel Dos Reis
2005-05-01  5:21 ` gdr at integrable-solutions dot net [this message]
     [not found] <bug-16370-1258@http.gcc.gnu.org/bugzilla/>
2007-03-21 14:39 ` ian at airs dot com
2007-05-17 16:22 ` bkoz at gcc dot gnu dot org
2007-09-23 15:27 ` jason at gcc dot gnu dot org
2007-09-23 15:28 ` jason at gcc dot gnu dot org
2007-09-23 15:28 ` jason 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=20050501052141.23139.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).