From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 579 invoked by alias); 14 Apr 2003 22:26:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 554 invoked by uid 71); 14 Apr 2003 22:26:00 -0000 Date: Mon, 14 Apr 2003 22:26:00 -0000 Message-ID: <20030414222600.553.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Wolfgang Bangerth Subject: Re: c/10406: Suggestion for variable attribute "default" Reply-To: Wolfgang Bangerth X-SW-Source: 2003-04/txt/msg00651.txt.bz2 List-Id: The following reply was made to PR c/10406; it has been noted by GNATS. From: Wolfgang Bangerth To: "Benjamin K." Cc: bangerth@dealii.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/