From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] Kill, kill, slay: banish sed, long live awk!
Date: Sun, 2 Jul 2023 22:01:34 +0100 [thread overview]
Message-ID: <845D3E29-1F92-45DE-B470-BCE1ABF7D08B@quintile.net> (raw)
In-Reply-To: <CABB-WO-_T6aW_cE_FrPK4_UtpoKSC_RhmKFk11uo=gYu6aZ5LQ@mail.gmail.com>
i think you are correct.
i have a distant memory that awk was one of the few bits of plan9 that did not work on a 386 without a 387.
-Steve
> On 2 Jul 2023, at 8:39 pm, Stuart Morrow <morrow.stuart@gmail.com> wrote:
>
> Can awk even build on (actual)386? (no floating point)
next prev parent reply other threads:[~2023-07-02 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 1:44 Amavect
2023-07-02 7:43 ` sirjofri
2023-07-02 16:17 ` Amavect
2023-07-02 18:32 ` Stuart Morrow
2023-07-02 21:01 ` Steve Simon [this message]
2023-07-03 22:46 ` Stuart Morrow
2023-08-01 5:36 ` mkf9
2023-08-01 22:10 ` [9front] Kill, kill, slay: banish sed, long live awk: Now historic plan9 Steve Simon
2023-08-02 4:56 ` Roberto E. Vargas Caballero
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=845D3E29-1F92-45DE-B470-BCE1ABF7D08B@quintile.net \
--to=steve@quintile.net \
--cc=9front@9front.org \
/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).