From: arnold@skeeve.com
To: 9fans@9fans.net
Subject: [9fans] doing a native awk port (was Re: Bug in print(2) g verb)
Date: Sun, 3 Mar 2013 11:54:57 -0700 [thread overview]
Message-ID: <201303031854.r23IsvYG029473@freefriends.org> (raw)
In-Reply-To: <6111fddc69b10b7ebad2e34fe9029fe0@yourdomain.dom>
Changing the subject here...
"Paul A. Patience" <paul-a.patience@polymtl.ca> wrote:
> ....
> for the native port of awk I am completing
> (started by boyd).
I was under the impression that awk was a native port, but I could
be wrong.
In any case, I recommend that you start with BWK's latest, which is
availble on github:
git clone git://github.com/onetrueawk/awk
And also talk to Erik who did some work on bringing the Plan 9 awk into
sync with BWK's a little while back.
HTH,
Arnold
P.S. The git repo includes his test suite in the file awktest.a; it should
probably be unarchived in a separate directory from the source.
next prev parent reply other threads:[~2013-03-03 18:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 2:49 [9fans] Bug in print(2) g verb Paul Patience
2013-03-01 0:08 ` Rob Pike
2013-03-01 2:57 ` Paul A. Patience
2013-03-01 4:54 ` Kurt H Maier
2013-03-01 15:30 ` Rob Pike
2013-03-01 15:58 ` Steve Simon
2013-03-01 17:38 ` Anthony Sorace
2013-03-01 22:53 ` Paul A. Patience
2013-03-03 17:33 ` erik quanstrom
2013-03-03 21:43 ` Richard Miller
2013-03-03 21:52 ` erik quanstrom
2013-03-03 18:54 ` arnold [this message]
2013-03-03 19:04 ` [9fans] doing a native awk port (was Re: Bug in print(2) g verb) Paul A. Patience
2013-03-03 19:08 ` erik quanstrom
2013-03-03 19:11 ` Kurt H Maier
2013-03-03 19:18 ` erik quanstrom
2013-03-03 19:28 ` Kurt H Maier
2013-03-03 19:31 ` erik quanstrom
2013-03-03 19:35 ` Kurt H Maier
2013-03-04 0:10 ` Dan Cross
2013-03-04 0:39 ` Kurt H Maier
2013-03-03 19:07 ` erik quanstrom
2013-03-03 21:29 ` Richard Miller
2013-03-03 21:38 ` erik quanstrom
2013-03-03 17:57 ` [9fans] Bug in print(2) g verb Paul A. Patience
2013-03-03 18:26 ` erik quanstrom
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=201303031854.r23IsvYG029473@freefriends.org \
--to=arnold@skeeve.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).