public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/10406: Suggestion for variable attribute "default"
Date: Mon, 14 Apr 2003 22:26:00 -0000	[thread overview]
Message-ID: <20030414222600.553.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/10406; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: "Benjamin K." <bkausbk@web.de>
Cc: bangerth@dealii.org, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Subject: Re: c/10406: Suggestion for variable attribute "default"
Date: Mon, 14 Apr 2003 17:24:28 -0500 (CDT)

 > It is at least same unimportant as some other attributes like
 > transparent_union, unused, deprecated or weak.
 
 Attribute unused is used in cases where in C++ you can write
   void f(int /*p*/) {
     ...; /* doesn't use p, but did in the past; we don't want to change 
             the prototype, though */
   }
 which you can't do in C.
 
 Deprecated was deemed useful enough to be included into the Java standard.
 
 Attribute weak changes the semantics of a function w.r.t. the linker.
 
 That being said, it might well be that some of the attributes are useless. 
 That should not tempt us into creating more uselessness, though.
 
 IMHO, your proposal is absolutely useless, since
 - one can get the same effect with a minimal change
 - it would have a ridiculously far-reaching impact since it would 
   essentially introduce overloading assignment operators in C.
 
 Wolfgang (certain to speak for the wider GCC community here)
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                                www: http://www.ices.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-04-14 22:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 22:26 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-14 22:16 Benjamin K.
2003-04-14 21:52 bangerth
2003-04-14 21:46 Benjamin Kalytta

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=20030414222600.553.qmail@sources.redhat.com \
    --to=bangerth@ices.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).