🚀 go-pugleaf

This problem should not exist in the next release of gcc.

> From: garp@isy.liu.se (Johan Garpendahl)
> Message-Id: <garp.708856796@isy.liu.se>
> Organization: Dept of EE, University of Linkoping
> Date: 18 Jun 92 08:39:56 GMT
> Apparently-To: gnu-g++-bug@sunic.sunet.se
> To: bug-g++@prep.ai.mit.edu

> I have found something that I think is a bug in g++-2.2.2
> The gcc-2.2.2 frontend does not complain.
> Good old 1.40 (gcc & g++) does not complain.

> I have an SS1+ with SunOS 4.1.1.

> main() {
>     const char* str = "String 1";
>     
>     /* This works */     
>     if (str == 0)
> 	str = "String 2";
>     else
> 	str = str;
>     
>     /* This fails */
>     /* assignment between incompatible pointer types */
>     str = (str == 0) ? "String 2" : str;
> }