bug-gawk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: fflush & close behavior not well-defined


From: pjfarley3
Subject: RE: fflush & close behavior not well-defined
Date: Mon, 14 Sep 2020 20:04:02 -0400

Apologies, I should have remembered I need to use "Reply All" in my mail
software to get the list address correctly populated.

Peter

> -----Original Message-----
> From: Andrew J. Schorr <aschorr@telemetry-investments.com>
> Sent: Monday, September 14, 2020 3:25 PM
> To: pjfarley3@earthlink.net
> Cc: bug-gawk@gnu.org
> Subject: Re: fflush & close behavior not well-defined
> 
> Thanks for responding, but please always group-reply to share your
thoughts
> with the list. I am cc'ing the list. This is not my decision to make.
> 
> Regards,
> Andy
> 
> On Mon, Sep 14, 2020 at 03:22:36PM -0400, pjfarley3@earthlink.net wrote:
> > FWIW, I care at least a little bit as well.  I like Wolfgang's
> > solution, including his caveat.
> >
> > "   close("| md5sum") # close pipe
> >    close(">md5sum" ) # close file
> > Unless, of course, this creates another ambiguity :-)"
> >
> > Second choice would be Manuel's suggestion of wrapper functions for
> > close along with your own suggestion of a close_coprocess() wrapper.
> >
> > But I must admit Arnold may be correct in this case.  If such issues
> > became truly serious for someone, it may be they are using the wrong
> > language to solve their problem.
> >
> > (g)awk isn't the universal solution after all, we just sometimes like
> > to pretend that it is.  :)
> >
> > Peter
--




reply via email to

[Prev in Thread] Current Thread [Next in Thread]