On 01.08.2022 11:48, Igenlode Wordsmith wrote:
[...] I fear you
under-estimate the degree of blissful ignorance of Windows in which it
is possible to exist..!
:-)
This whole process is like trying to debug a program by dictating the contents of a set of punched cards by telephone across the continent,
then waiting a week for the next allocated session of computer time
before you have any feedback on what went wrong this time... [...]
Not far from how we worked back in the 1980's. ;-)
You know punch-cards; that lets me make a guess about your engagement
time range with computers. - How did you manage to completely ignore
or avoid WinDOS since decades? - I'm really curious, since management
sooner or later very often seems to force their folks to use it. It's
hard to avoid even if you're on the holy war path of an Unix apologist
or evangelist.
Since it's about Windows I haven't followed this thread too closely.
From what I've seen you probably want a solution with an GNU Awk that
is either statically linked or has just the executable with the two
(or was it three) necessary libraries from the Cygwin package. I went
the second path (quite some time ago), and Bruce seems to have shown
a way for the former path. WRT to the question about the size of the executable; that's hard to say without knowing details. A huge file
may indicate a statically linked executable (with a library layer to
access the Unix or POSIX functions), or a file that is not stripped
from the list of names used for debugging. A small executable might
dynamically access the required libraries. Maybe this Unix subsystem
thing that you may get with newer Windows versions already contains
these libraries? (Just speculating.)
Janis
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)