Re: c++/2112

Re: c++/2112

[Nathan Sidwell]

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

From: Nathan Sidwell <nathan@codesourcery.com>
To: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
Cc: nathan@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: c++/2112
Date: Mon, 18 Nov 2002 12:25:23 +0000

 Wolfgang Bangerth wrote:
 > Nathan,
 > you marked this report as confirmed. How strongly do you feel about this? 
 > I think the message I get is actually not wrong, so at the most I would 
 > concede to make it a feature-request and mark it as that (and maybe put it 
 > in suspended mode?). I agree that the message 2.95 (the lower one below) 
 I don't feel strongly. an analyzed feature request would be fin.
 
 nathan
 
 -- 
 Dr Nathan Sidwell   ::   http://www.codesourcery.com   ::   CodeSourcery LLC
           'But that's a lie.' - 'Yes it is. What's your point?'
 nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
 
 

Re: c++/2112

[Wolfgang Bangerth]

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nathan@gcc.gnu.org
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/2112
Date: Thu, 14 Nov 2002 15:34:35 -0600 (CST)

 Nathan,
 you marked this report as confirmed. How strongly do you feel about this? 
 I think the message I get is actually not wrong, so at the most I would 
 concede to make it a feature-request and mark it as that (and maybe put it 
 in suspended mode?). I agree that the message 2.95 (the lower one below) 
 is more accurate, but I think the one we now get is also ok.
 
 Regards
   Wolfgang
 
 tmp/g> cat y.cc
 struct X;
 
 void f (int &);
 void f (X);
 void g () {f(1); };
 
 
 tmp/g> /home/bangerth/bin/gcc-3.3x-pre/bin/c++ -c y.cc
 y.cc: In function `void g()':
 y.cc:5: error: no matching function for call to `f(int)'
 y.cc:3: error: candidates are: void f(int&)
 y.cc:4: error:                 void f(X)
 
 
 tmp/g> c++ -c y.cc
 y.cc: In function `void g()':
 y.cc:5: initialization of non-const reference type `int &'
 y.cc:5: from rvalue of type `int'
 y.cc:3: in passing argument 1 of `f(int &)'
 
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 

Re: c++/2112

[nathan]

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

From: nathan@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, richarda@ixla.com.au
Cc:  
Subject: Re: c++/2112
Date: 27 Apr 2001 15:07:57 -0000

 Synopsis: Diagnostic message misleading for binding r-value to non-const reference
 
 State-Changed-From-To: open->analyzed
 State-Changed-By: nathan
 State-Changed-When: Fri Apr 27 11:07:56 2001
 State-Changed-Why:
     confirmed as a bug
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2112&database=gcc