This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: cannot convert `int ()()' to `void' in initialization - should not be an error

To: Alexandre Oliva <aoliva at redhat dot com>
Subject: Re: cannot convert `int (*)()' to `void*' in initialization - should not be an error
From: Carlo Wood <carlo at alinoe dot com>
Date: Thu, 31 May 2001 21:13:42 +0200
Cc: "Stuehlmeyer, Wolfgang" <Wolfgang dot Stuehlmeyer at softwareag dot com>, "'gcc-bugs at gcc dot gnu dot org'" <gcc-bugs at gcc dot gnu dot org>
References: <2B1792E820ACD411AD5A00508BF9A3FC369107@daemsg03.software-ag.de> <orzobt1wt8.fsf@guarana.lsd.ic.unicamp.br>

On Thu, May 31, 2001 at 10:18:27AM -0300, Alexandre Oliva wrote:
> They were in error.  GCC 3.0 is correct.  C++ doesn't allow implicit
> conversion from function types to void*.

I noticed this too (and had to add a cast).  What is the reason
that C++ doesn't allow this?  I don't like casts, they normally
lead to bugs later on.  What is the pitfal in this case?  Probably
the same as the reason that C++ forbids it.

-- 
Carlo Wood <carlo@alinoe.com>

Follow-Ups:
- Re: cannot convert `int (*)()' to `void*' in initialization - should not be an error
  - From: Gabriel Dos Reis
- Re: cannot convert `int (*)()' to `void*' in initialization - should not be an error
  - From: DJ Delorie

References:
- cannot convert `int (*)()' to `void*' in initialization - should not be an error
  - From: Stuehlmeyer, Wolfgang
- Re: cannot convert `int (*)()' to `void*' in initialization - should not be an error
  - From: Alexandre Oliva

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: cannot convert `int (*)()' to `void*' in initialization - should not be an error

Re: cannot convert `int ()()' to `void' in initialization - should not be an error