[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: fflush & close behavior not well-defined
From: |
Andrew J. Schorr |
Subject: |
Re: fflush & close behavior not well-defined |
Date: |
Wed, 30 Sep 2020 12:29:34 -0400 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Wed, Sep 30, 2020 at 01:14:46AM -0600, arnold@skeeve.com wrote:
> arnold@skeeve.com wrote:
>
> > "Andrew J. Schorr" <aschorr@telemetry-investments.com> wrote:
> >
> > > On Tue, Sep 15, 2020 at 06:59:27AM +0000, Lorenz via Bug reports and all
> > > discussion about gawk. wrote:
> > > > would gawk warning about such ambiguitiies be an option? At least in
> > > > --lint mode?
> > > > --
> > >
> > > I like that idea; I'd vote for issuing the warning regardless of whether
> > > --lint is set.
> >
> > I'm working on this. It'll be with --lint.
>
> This is done and in gawk-5.1-stable and in master. See the iolint
> test in the test suite.
Thanks. But I get a test failure on my system:
============== _iolint =============
*** iolint.ok 2020-09-30 10:04:43.043452000 -0400
--- _iolint 2020-09-30 12:27:17.751540000 -0400
***************
*** 27,34 ****
gawk: ./iolint.awk:59: warning: `cat' used for output pipe and two-way pipe
gawk: ./iolint.awk:59: warning: `cat' used for output file and two-way pipe
hello
! gawk: ./iolint.awk:60: warning: failure status (141) on two-way pipe close of
`cat': Success
! 141
0
0
gawk: ./iolint.awk:67: warning: `echo hello' used for input pipe and output
pipe
--- 27,34 ----
gawk: ./iolint.awk:59: warning: `cat' used for output pipe and two-way pipe
gawk: ./iolint.awk:59: warning: `cat' used for output file and two-way pipe
hello
! gawk: ./iolint.awk:60: warning: failure status (269) on two-way pipe close of
`cat': Success
! 269
0
0
gawk: ./iolint.awk:67: warning: `echo hello' used for input pipe and output
pipe
Tihs is on CentOS 7.8.
Regards,
Andy
- Re: fflush & close behavior not well-defined, (continued)
- Re: fflush & close behavior not well-defined, Andrew J. Schorr, 2020/09/14
- Re: fflush & close behavior not well-defined, Neil R. Ormos, 2020/09/14
- Re: fflush & close behavior not well-defined, Andrew J. Schorr, 2020/09/14
- Message not available
- Re: fflush & close behavior not well-defined, Andrew J. Schorr, 2020/09/14
- RE: fflush & close behavior not well-defined, pjfarley3, 2020/09/14
- Re: fflush & close behavior not well-defined, Wolfgang Laun, 2020/09/14
Re: fflush & close behavior not well-defined, Lorenz, 2020/09/15
- Re: fflush & close behavior not well-defined, Andrew J. Schorr, 2020/09/15
- Re: fflush & close behavior not well-defined, arnold, 2020/09/15
- Re: fflush & close behavior not well-defined, arnold, 2020/09/30
- Re: fflush & close behavior not well-defined,
Andrew J. Schorr <=
- Re: fflush & close behavior not well-defined, arnold, 2020/09/30
- Re: fflush & close behavior not well-defined, Andrew J. Schorr, 2020/09/30
- Re: fflush & close behavior not well-defined, arnold, 2020/09/30
- Re: fflush & close behavior not well-defined, Andrew J. Schorr, 2020/09/30
Re: fflush & close behavior not well-defined, Nelson H. F. Beebe, 2020/09/14