Re: A feature I'd like to see in GAWK...

In article <v76jr4$tu3$1@nnrp.usenet.blueworldhosting.com>,
Arti F. Idiot <addr@is.invalid> wrote:

On 7/15/24 12:28 PM, Kenny McCormack wrote:

I think something like the above would be more in line with the sort of
things I'd like to see in GAWK.

>
+1 ; great idea.

Well, I think so.  The idea is that you shouldn't have to give up the most
intrinsic part of AWK (the pattern/action paradigm) just because your input
isn't a named (i.e., on the command line) file.

I think of it as "rehabilitating getline".  Bringing it back into the fold,
rather than exiling it to the sidelines.

Note also that my "pipeline" extension only handles the case of a simple
process (either input or output - i.e., like AWK's "getline" and "print"
with "|" redirection).  It doesn't handle any of the other variations of
getline/print - such as the ones that interface with network sockets.  It
would be nice if a built-in approach did those things as well (and better
than my extension does).

--
The randomly chosen signature file that would have appeared here is more than 4
lines long.  As such, it violates one or more Usenet RFCs.  In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/FreeCollege