From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon, 19 Apr 2010 12:45:34 -0400
To: 9fans@9fans.net
Message-ID: <371d507561ee5d4bcd39f397d061aede@ladd.quanstro.net>
In-Reply-To: <v2ia560a5d01004190938jb4e241dclf138fb3bf1dfe0a@mail.gmail.com>
References: <u2wa560a5d01004190829r8eb8feb2xe145cd391aa3a605@mail.gmail.com>
	<fe786951a263337f9387eb379ba88085@coraid.com>
	<v2ia560a5d01004190938jb4e241dclf138fb3bf1dfe0a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] plan9port awk problem
Topicbox-Message-UUID: 09500be4-ead6-11e9-9d60-3106f5b1d025

> 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.  it produces the same
output as you produced for p9p awk.  if 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:

	;9 awk 'BEGIN {OFMT="%.0f"; print 17.23}'
	17.23
	;awk 'BEGIN {OFMT="%.0f"; print 17.23}'
	17

and here's what the awk as distributed on sources does
	minooka; /n/sources/plan9/386/bin/awk 'BEGIN {OFMT="%.0f"; print 17.23}'
	17.23

yet here's what the awk done with bwk's current sources does
	minooka; awk 'BEGIN {OFMT="%.0f"; print 17.23}'
	17

- erik