c++/396: const int null = 0;

c++/396: const int null = 0;

[Wolfgang Bangerth]

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

From: Wolfgang Bangerth <bangerth@apex68.ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: c++/396: const int null = 0;
Date: Thu, 14 Nov 2002 14:32:21 -0600

 Re-confirmed with 3.3 CVS from 2002-11-10 and 3.2.1 pre from the same date.

Re: c++/396: const int null = 0;

[Wolfgang Bangerth]

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: c++/396: const int null = 0;
Date: Tue, 22 Oct 2002 17:40:47 -0500 (CDT)

 I don't actually know what the standard would mandate in this case 
 (conversion from 'const int &' to 'int *'), but this is clearly at least 
 confusing (stripped down and condensed testcase from this report):
 -----------------------------------
 void f(int* pn);
 
 struct Foo {
     static void f(int* pn);
 };
 
 int main() {
   const int null = 0;
 
   f(0);    // ok
   f(null); // ok
   
   Foo::f(0);    // ok
   Foo::f(null); // compile error
 }
 ----------------------------------
 The compiler only gives an error on the call to Foo::f(), not on ::f(), 
 although they have the same signature. For present CVS and 3.2, the error 
 message is
 x.cc: In function `int main()':
 x.cc:14: error: invalid conversion from `int' to `int*'
 x.cc:14: error:   initializing argument 1 of `static void Foo::f(int*)'
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth