From: Kaz Kylheku <920-082-4242@kylheku.com>
To: cygwin@cygwin.com
Subject: Re: Where is igawk and why doesn't @include replicate this feature?
Date: Thu, 12 Sep 2019 03:00:00 -0000 [thread overview]
Message-ID: <f91809f47f6caa1211e93afaaffe77e6@mail.kylheku.com> (raw)
In-Reply-To: <CAC9BAENxZs7ZwSHz1Xq0DAxP0tS6R4fUQ6Rv_tEG_qrCsOZTew@mail.gmail.com>
On 2019-09-10 23:54, Troy Kenah wrote:
> Hi All,
>
> I have a large number of scripts that were using the the igawk script,
> however I have updated my gawk to a newer release that has
> obsoleted/removed the igawk script.
Gawk's build system stopped installing igawk over five years ago:
http://git.savannah.gnu.org/cgit/gawk.git/commit/?id=577ece63770a6c4b5ad00d6998127fb7e85b86b9
> I used to embed @include junk.awk statements to reduce repetitive code
> but
> this no longer works. These were files were not functions, simply code
> snippets; this is the type of error I am now seeing:
Clearly, the script is not exactly obsolete, since the @include facility
in
Gawk seems only to work with syntactically complete units, whereas
igawk performs blind textual inclusion.
If I were you, I'd just bring the igawk script into my code base and
continue that way. It's a tiny script that is licensed as
public domain; it doesn't carry much "technical debt" or licensing
debt.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-09-11 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 11:52 Troy Kenah
2019-09-11 14:27 ` Steven Penny
2019-09-12 5:18 ` Brian Inglis
2019-09-11 18:10 ` Achim Gratz
2019-09-12 3:00 ` Kaz Kylheku [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f91809f47f6caa1211e93afaaffe77e6@mail.kylheku.com \
--to=920-082-4242@kylheku.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).