From owner-freebsd-current  Thu Apr  6 08:33:03 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id IAA29793
          for current-outgoing; Thu, 6 Apr 1995 08:33:03 -0700
Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA29785
          for <freebsd-current@FreeBSD.org>; Thu, 6 Apr 1995 08:32:57 -0700
Received: by sovcom.kiae.su id AA01630
  (5.65.kiae-2  for freebsd-current@FreeBSD.org); Thu, 6 Apr 1995 19:22:29 +0400
Received: by sovcom.KIAE.su (UUMAIL/2.0); Thu,  6 Apr 95 19:22:27 +0300
Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id TAA02904; Thu, 6 Apr 1995 19:15:44 +0400
To: freebsd-current@FreeBSD.org, "Nickolay N. Dudorov" <nnd@gw.itfs.nsk.su>
References: <199504061324.UAA10720@gw.itfs.nsk.su>
In-Reply-To: <199504061324.UAA10720@gw.itfs.nsk.su>;
    from "Nickolay N. Dudorov" at Thu, 6 Apr 1995 20:24:44 +0700
Message-Id: <MNWM0XlOpB@astral.msk.su>
Organization: Olahm Ha-Yetzirah
Date: Thu,  6 Apr 1995 19:15:44 +0400
X-Mailer: Mail/@ [v2.32 FreeBSD]
From: "Andrey A. Chernov, Black Mage" <ache@astral.msk.su>
X-Class: Fast
Subject: Re: PERL4&5 broken in -current and 950322-SNAP!
Lines: 50
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 1327
Sender: current-owner@FreeBSD.org
Precedence: bulk

In message <199504061324.UAA10720@gw.itfs.nsk.su> Nickolay N. Dudorov
    writes:

>>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.

I think, we still have a bug here.
Why 1 instead of 1. ?
And more generic why: I think it should be
1.0
0.0
or return to
1
0
(SunOS and ISC can be treated as some kind of standard behaviour)

>(Test program :

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

-- 
Andrey A. Chernov        : And I rest so composedly,  /Now, in my bed,
ache@astral.msk.su       : That any beholder  /Might fancy me dead -
FidoNet: 2:5020/230.3    : Might start at beholding me,  /Thinking me dead.
RELCOM Team,FreeBSD Team :         E.A.Poe         From "For Annie" 1849