9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Benjamin Purcell <benjapurcell@gmail.com>
To: 9front@9front.org
Subject: New Regular Expression Library
Date: Thu, 28 Apr 2016 08:41:09 -0500	[thread overview]
Message-ID: <CAAsuYKeiKHji4m6WzAPPxbZ9rJk5tuv-JJQ2fhOGsY_z2Wt7tg@mail.gmail.com> (raw)

I have prepared a mercurial bundle that contains the following changes:

1. A new regular expression library.
2. A port of awk to native plan 9.
3. APE regular expression library is removed (only AWK was using it).

The bundle is available at /n/contrib/spew/libregexp.bundle and is
relative to revision f385a29db7f1.

The new regular expression library is faster, uses less memory for
small regular expressions, and will not fail to find matches on
complicated regular expressions that cause the old library to fail.

Porting awk to native plan 9 means awk gets to use the new library.
There is no reason to keep the APE library around since it is snarfed
directly from the old library, it does not implement POSIX libregex
syntax or semantics, and nothing else uses it. I have run bwk's
regression on the new awk, and the only changes are that two floating
point calculations differ by one in the 100ths place and the new awk
succeeds on a couple regular expressions that the old one fails on.

I have been this library in the system for a while now, and it has
seen a good amount of use (in mk, sed, awk, and the plumber) due to
the awk regression suite, numerous full system compilations, and
general usage. I have observed no changes in the system.

Thanks,
spew


             reply	other threads:[~2016-04-28 13:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 13:41 Benjamin Purcell [this message]
2016-04-28 14:19 ` [9front] " Kurt H Maier
2016-04-28 14:22   ` Benjamin Purcell

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=CAAsuYKeiKHji4m6WzAPPxbZ9rJk5tuv-JJQ2fhOGsY_z2Wt7tg@mail.gmail.com \
    --to=benjapurcell@gmail.com \
    --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).