[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gawk] Win32 Gawk 4.0.0 bugs
From: |
Aharon Robbins |
Subject: |
Re: [bug-gawk] Win32 Gawk 4.0.0 bugs |
Date: |
Tue, 08 Nov 2011 21:01:50 +0200 |
User-agent: |
Heirloom mailx 12.4 7/29/08 |
Hi. Re this:
> From: Giorgio Palandri <address@hidden>
> Date: Mon, 7 Nov 2011 21:48:43 +0100
> To: address@hidden
> Subject: [bug-gawk] Win32 Gawk 4.0.0 bugs
Going to the second bug first:
> The second bug is in DGAWK: if I set a breakpoint OUTSIDE of a switch
> statement, all works fine.
> If I set a breakpoint INSIDE a switch statement the breakpoint is set
> on a following line (the increment seems arbitrary).
I'm not sure about this - John, can you look at it?
> Hi; maybe I've found two bugs in gawk 4.0.0 for Windows. The first one
> is in sprintf function (see following text):
>
> THE SOURCE PROGRAM
> ------------------------------------------------------
>
> C:\tmp>type test.awk
>
> BEGIN {
> c = 100
> z = sprintf("%05s", c)
> print z
> }
The '0' flag no longer applies to the non-numeric formats (%c and %s).
This is documented and intentional; gawk is "keeping up with" C, which
changed at some point. It was pretty silly to have the '0' flag
apply to %s in the first place, but I was just following the then-current
C standard.
Thanks for the report. We'll look into the dgawk issue.
Arnold