From owner-freebsd-current  Thu Apr  6 09:33:56 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id JAA01598
          for current-outgoing; Thu, 6 Apr 1995 09:33:56 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA01573
          for <freebsd-current@freebsd.org>; Thu, 6 Apr 1995 09:33:37 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA26669; Fri, 7 Apr 1995 02:29:28 +1000
Date: Fri, 7 Apr 1995 02:29:28 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199504061629.CAA26669@godzilla.zeta.org.au>
To: freebsd-current@FreeBSD.org, nnd@gw.itfs.nsk.su
Subject: Re: PERL4&5 broken in -current and 950322-SNAP!
Sender: current-owner@FreeBSD.org
Precedence: bulk

>>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);
>}

Fixed.  vfprintf() was broken.  Thanks for the bug report.

Bruce