public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Benjamin K." <bkausbk@web.de>
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:16:00 -0000	[thread overview]
Message-ID: <20030414221600.26564.qmail@sources.redhat.com> (raw)

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

From: "Benjamin K." <bkausbk@web.de>
To: <bangerth@dealii.org>,
	<bkausbk@web.de>,
	<gcc-bugs@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>,
	<gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: c/10406: Suggestion for variable attribute "default"
Date: Tue, 15 Apr 2003 00:14:46 +0200

 It is at least same unimportant as some other attributes like
 transparent_union, unused, deprecated or weak.
 
 Benjamin Kalytta
 
 
 > Synopsis: Suggestion for variable attribute "default"
 > 
 > State-Changed-From-To: open->closed
 > State-Changed-By: bangerth
 > State-Changed-When: Mon Apr 14 21:52:17 2003
 > State-Changed-Why:
 >     Will absolutely certainly not be implemented in gcc unless
 >     some standards body agrees that this is useful. Which is just
 >     as well very doubtful. This extension doesn't add anything
 >     at all that could not be done in a very simple way with
 >     other means.
 >     
 >     W.
 >     
 >     BTW: Use C++, there you can overload the assignement operator.
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10406


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 22:16 Benjamin K. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-14 22:26 Wolfgang Bangerth
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=20030414221600.26564.qmail@sources.redhat.com \
    --to=bkausbk@web.de \
    --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).