🚀 go-pugleaf

According to basti@orthogo.UUCP:
>I just reinstalled gcc-2.2.2 on our RS6000 (configured rs6000-ibm-aix) and
>stumbled again over this damn bug within __builtin_new of libgcc2.c:
>Allocating e.g., new int[0], fires the new_handler!

According to chip@tct.com (Chip Salzenberg):
>You're fixing the wrong thing.  Instead of allowing malloc() to return
>NULL without complaint, you should say "p = malloc (sz ? sz : 1)".

Chip, you're wrong. The ARM is quite specific in this case. On page 280
it says:
	If operator new() cannot allocate storage or if it is called
	with the argument 0 it will return 0.
and:
	If operator new() cannot find storage to return, it calls
	a function -- often referred to a the new-handler -- [...].

Calling operator new() with an argument of 0 should thus return 0 WITHOUT
calling the new-handler (which is, by the way, also the behavior of all
the other C++ compilers).

Sebastian Wangnick   Orthogon System GmbH
(basti@orthogo.uucp) Linzer Strasse 4
Tel +49 421 219136   D-2800 Bremen 33
Fax +49 421 213093   Germany