From owner-freebsd-current  Thu Apr  6 03:24:41 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id DAA22712
          for current-outgoing; Thu, 6 Apr 1995 03:24:41 -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 DAA22704
          for <freebsd-current@freebsd.org>; Thu, 6 Apr 1995 03:24:24 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id UAA16925; Thu, 6 Apr 1995 20:18:44 +1000
Date: Thu, 6 Apr 1995 20:18:44 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199504061018.UAA16925@godzilla.zeta.org.au>
To: freebsd-current@FreeBSD.org, taob@gate.sinica.edu.tw
Subject: Re: PERL4&5 broken in -current and 950322-SNAP!
Sender: current-owner@FreeBSD.org
Precedence: bulk

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

Bruce