From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Where is igawk and why doesn't @include replicate this feature?
Date: Wed, 11 Sep 2019 18:10:00 -0000 [thread overview]
Message-ID: <877e6ek9iq.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAC9BAENxZs7ZwSHz1Xq0DAxP0tS6R4fUQ6Rv_tEG_qrCsOZTew@mail.gmail.com> (Troy Kenah's message of "Wed, 11 Sep 2019 16:54:49 +1000")
Troy Kenah writes:
> 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.
The semantics for @include are different between igawk and "native" gawk
@include (since 4.x). The newer gawk versions treat @include statements
like they would treat the --include option on the command line. In
particular that means that each include is processed only once and you
should (only) use it to define functions.
The igawk script was removed from gawk in this commit
http://git.savannah.gnu.org/cgit/gawk.git/commit/?id=577ece63770a6c4b5ad00d6998127fb7e85b86b9
but left in the manual, so you can resurrect it either from there or
from Git:
http://git.savannah.gnu.org/cgit/gawk.git/plain/awklib/eg/prog/igawk.sh
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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
next prev parent reply other threads:[~2019-09-11 17:50 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 [this message]
2019-09-12 3:00 ` Kaz Kylheku
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=877e6ek9iq.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).