public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/1628
@ 2001-05-01  6:56 nathan
  0 siblings, 0 replies; 2+ messages in thread
From: nathan @ 2001-05-01  6:56 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

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

From: nathan@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org,
  wolfgang.bangerth@iwr.uni-heidelberg.de
Cc:  
Subject: Re: c++/1628
Date: 1 May 2001 13:54:52 -0000

 Synopsis: Bogus (but annoying) warning about unused parameter
 
 State-Changed-From-To: analyzed->closed
 State-Changed-By: nathan
 State-Changed-When: Tue May  1 09:54:52 2001
 State-Changed-Why:
     fixed
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1628&database=gcc


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: c++/1628
@ 2001-04-01  0:00 Wolfgang Bangerth
  0 siblings, 0 replies; 2+ messages in thread
From: Wolfgang Bangerth @ 2001-04-01  0:00 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

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

From: Wolfgang Bangerth <wolfgang.bangerth@iwr.uni-heidelberg.de>
To: rodrigc@gcc.gnu.org
Cc: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c++/1628
Date: Tue, 13 Mar 2001 14:43:23 +0100 (MET)

 Hi,
 
 On 13 Mar 2001 rodrigc@gcc.gnu.org wrote:
 > Synopsis: Bogus (but annoying) warning about unused parameter
 >     The parameter is unused.
 
 No, its not, since at the point where the warning is printed (in the
 _declaration_ of the function) I can never use the variable. The only
 place where such a warning should occur is at the point of _definition_ of
 a function (where I _can_ use the variable), which is where I
 intentionally refrained from assigning the variable a name.
 
 >     You can remove the variable i
 >     from your function declaration:
 >     class X{  X(int); }
 
 Of course I can, but this is not my intention, as I want to document the
 purpose of this parameter by assigning it a name. This is common practice
 and has worked with all previous gcc versions.
 
 
 >     Or in your function definition you could add something like:
 >     X(int i){  if(i){} }
 
 Again, of course I can do that but it is not my intention to introduce a
 stray `if(something)' because I have assigned a variable a name somewhere
 else in my program.
 
 I still insist on the fact that this message is bogus and should be
 removed.
 
 Best regards
   Wolfgang
 
 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1628&database=gcc
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth          email: wolfgang.bangerth@iwr.uni-heidelberg.de
                              www: http://gaia.iwr.uni-heidelberg.de/~wolf
 
 
 


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-05-01  6:56 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-05-01  6:56 c++/1628 nathan
  -- strict thread matches above, loose matches on Subject: below --
2001-04-01  0:00 c++/1628 Wolfgang Bangerth

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).