🚀 go-pugleaf

I have some questions about gawk.  I appreciate any answers anybody
can provide.

1.  Is it faster than awk, nawk, perl?  Does it have fewer memory
    (program size) limitations?

    How many passes through the source does it make?

2.  Is it easily modifiable?  How does it compare to nawk?

    How easy will it be to add some operators, a few built-in
    functions, and function pointers?

    How easy will it be to add a C call function?  (Ah, now you see
    why I'm asking these questions :-).)  How about some kind of
    dynamic linking and calling (I presume that this is no big deal on
    gawk's side of things)?

    How easy will it be to add some C++-style default argument values
    for variable-argument built-in functions?  How easy would function
    overloading be to implement?  How about overloading of built-ins?

    How easy will it be to add a require/provide and/or an autoload
    facility?  How easy will it be to deallocate one program's memory
    and to load another in its place?

2.5 Is there a rewind or a skip, or an ungetline (IMHO a vacancy in
    nawk)?

3.  Is there a compiler or a gawk to C translator?  Is there one in
    the works?  How easy would it be to do a byte-compile style operation?

    Are there software development tools to go along with it?  Is
    there an emacs gawk-mode?

4.  Has it been ported to UTS (a big mainframe UNIX)?  Has it been
    ported to HP-UX?

5.  Is its author listening?

6.  Where can I get it _using email_?

I don't read this newsgroup; please let me know by email if this is an
inappropriate place to ask these questions, and email any replies if
possible.  I didn't see a gnu.misc, so I presume that this is OK.

Thanks.
--
If you do not receive a reply from me, please resend your mail;
occasionally this site's mail gets delayed.

Neither representing any company nor, necessarily, myself.