From owner-freebsd-current  Thu Apr  6 07:08:23 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id HAA27466
          for current-outgoing; Thu, 6 Apr 1995 07:08:23 -0700
Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA27448
          for <freebsd-current@FreeBSD.org>; Thu, 6 Apr 1995 07:08:07 -0700
Received: from localhost (nnd@localhost) by gw.itfs.nsk.su (8.6.4/8.6.4) id UAA10720 for freebsd-current@FreeBSD.org; Thu, 6 Apr 1995 20:24:44 +0700
Date: Thu, 6 Apr 1995 20:24:44 +0700
From: "Nickolay N. Dudorov" <nnd@gw.itfs.nsk.su>
Message-Id: <199504061324.UAA10720@gw.itfs.nsk.su>
To: freebsd-current@FreeBSD.org
Subject: Re: PERL4&5 broken in -current and 950322-SNAP!
Sender: current-owner@FreeBSD.org
Precedence: bulk

>From: Bruce Evans <bde@zeta.org.au>

>>    The first loop prints out a "0." instead of a "0".  This anomaly
>>also caused gcc to fail when compiling the extension modules (because
>>perl was generating array subscripts with 0. instead of 0).  Anyone
>>have a gcc 2.6.2/pre-950322 machine to test this?

>The C printf function used to print "0" in some cases when it should
>have printed "0.".  Apparently perl's tests expect the broken behaviour.

	This is very strange but on FreeBSD-1.1.5.1, FreeBSD-2.0-950210-SNAP,
SunOS 4.1.3 and ISC 3.0 my test program prints:

1
0

and only on FreeBSD-current I see:

1
0.

(Test program :

main()
{
char b[256];
sprintf(b,"%g",1.0);
printf("%s\n",b);
sprintf(b,"%g",0.0);
printf("%s\n",b);
}

		N.Dudorov