From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Where is igawk and why doesn't @include replicate this feature?
Date: Wed, 11 Sep 2019 14:27:00 -0000 [thread overview]
Message-ID: <5d78dfe7.1c69fb81.686f1.9f87@mx.google.com> (raw)
In-Reply-To: <CAC9BAENxZs7ZwSHz1Xq0DAxP0tS6R4fUQ6Rv_tEG_qrCsOZTew@mail.gmail.com>
On Wed, 11 Sep 2019 16:54:49, Troy Kenah wrote:
> 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:
>
> gawk: get_FY2019Q1OIC.awk:28: @include "../inc/segments.awk"
> gawk: get_FY2019Q1OIC.awk:28: ^ syntax error
> gawk: get_FY2019Q1OIC.awk:36: fromdate=mktime("2019 09 01 00 00 00")
> gawk: get_FY2019Q1OIC.awk:36: ^ syntax error
> gawk: get_FY2019Q1OIC.awk:36: fromdate=mktime("2019 09 01 00 00 00")
> gawk: get_FY2019Q1OIC.awk:36:
> ^ 0 is invalid as number of arguments for mktime
Works fine here:
$ gawk --version
GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.1.2)
$ cat one.awk
function f1(n1) {
return n1 + 10
}
$ cat two.awk
@include "one.awk"
BEGIN {
print f1(20)
}
$ unset POSIXLY_CORRECT
$ gawk -f two.awk
30
Finally, I would make a suggestion. "@include" is not POSIX, so if you find
yourself relying on something like this more and more, it might be better to
switch to a proper programming language. Something like Perl, Lua or Tcl.
--
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 11:52 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 [this message]
2019-09-12 5:18 ` Brian Inglis
2019-09-11 18:10 ` Achim Gratz
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=5d78dfe7.1c69fb81.686f1.9f87@mx.google.com \
--to=svnpenn@gmail.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).