From: arnold@skeeve.com
To: 9fans@9fans.net, 23hiro@gmail.com
Subject: Re: [9fans] updating awk ...
Date: Tue, 28 Aug 2018 01:18:35 -0600 [thread overview]
Message-ID: <201808280718.w7S7IaET006077@freefriends.org> (raw)
In-Reply-To: <CAFSF3XM3UpYRWtYNj5_qYHwARz9ttS=Pi27DS1dDQgw+mttUSQ@mail.gmail.com>
Thanks for the info.
I may pull the iso to take a look.
In any case, for those using BWK's awk, it's worth pulling in the
latest set of changes, they're not huge.
Thanks,
Arnold
hiro <23hiro@gmail.com> wrote:
> spew is a 9front user who wanted to improve awk.
>
> there is no separate hg location, branch, etc., awk is in the default
> branch of 9front.
>
> i don't know if he wasted a thought on unix while he was doing that,
> better ask him: he's on #cat-v on freenode regularly.
>
> the 9front distribution .iso contains the complete hg repo with all
> the history, so if you can run our awk, you also have the source and
> the history.
> his efforts started with the regexp library that used to require ape!
> the first related commits i found are:
>
> changeset: 5271:9bf761f83f7e
> branch: spew
> user: ben@rana
> date: Wed Apr 27 07:52:41 2016 -0500
> summary: remove ape regexp library, add utility for awk native port
>
> changeset: 5269:cad63b966180
> branch: spew
> parent: 5266:682b1efdef40
> user: ben@rana
> date: Tue Apr 26 22:23:44 2016 -0500
> summary: New libregexp and APE ported to native
>
> replying to list in case others want to understand, too.
next prev parent reply other threads:[~2018-08-28 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 18:43 Arnold Robbins
2018-08-27 21:13 ` hiro
2018-08-28 6:52 ` hiro
2018-08-28 7:18 ` arnold [this message]
2018-08-29 4:40 ` Benjamin Purcell
2018-08-29 14:55 ` Kurt H Maier
2018-08-30 6:59 ` Pumba The Pig
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=201808280718.w7S7IaET006077@freefriends.org \
--to=arnold@skeeve.com \
--cc=23hiro@gmail.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).