From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <371d507561ee5d4bcd39f397d061aede@ladd.quanstro.net>
References: <u2wa560a5d01004190829r8eb8feb2xe145cd391aa3a605@mail.gmail.com>
	<fe786951a263337f9387eb379ba88085@coraid.com>
	<v2ia560a5d01004190938jb4e241dclf138fb3bf1dfe0a@mail.gmail.com>
	<371d507561ee5d4bcd39f397d061aede@ladd.quanstro.net>
Date: Mon, 19 Apr 2010 18:50:42 +0200
Message-ID: <j2ma560a5d01004190950y8bbe7a62w7b1884c23ee99892@mail.gmail.com>
From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] plan9port awk problem
Topicbox-Message-UUID: 0959664e-ead6-11e9-9d60-3106f5b1d025

On 19 April 2010 18:45, erik quanstrom <quanstro@quanstro.net> wrote:
>> I don't get it.
>> As I said, awk in plan9 works ok in the mentioned respect.
>> I said that plan9port awk gets it wrong for some reason...
>>
>> R
>
> i just ran awk from sources. =A0it produces the same
> output as you produced for p9p awk. =A0if you say
> that p9p awk is wrong, then plan 9 awk is wrong
> too since it produces the same output.
>
> here's what you had:
>
> =A0 =A0 =A0 =A0;9 awk 'BEGIN {OFMT=3D"%.0f"; print 17.23}'
> =A0 =A0 =A0 =A017.23
> =A0 =A0 =A0 =A0;awk 'BEGIN {OFMT=3D"%.0f"; print 17.23}'
> =A0 =A0 =A0 =A017
>
> and here's what the awk as distributed on sources does
> =A0 =A0 =A0 =A0minooka; /n/sources/plan9/386/bin/awk 'BEGIN {OFMT=3D"%.0f=
"; print 17.23}'
> =A0 =A0 =A0 =A017.23
>
> yet here's what the awk done with bwk's current sources does
> =A0 =A0 =A0 =A0minooka; awk 'BEGIN {OFMT=3D"%.0f"; print 17.23}'
> =A0 =A0 =A0 =A017
>
> - erik
>
>
Then something strange must have happened recently...
Or something like that.
I had checked and now did it again, on my plan 9 computer, that I get 17.
R