The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Arnold Robbins <arnold@skeeve.com>
To: tuhs@tuhs.org
Subject: [TUHS] Doug McIlroy's C++ regular expression library (mostly) revived
Date: Sun, 22 Jul 2018 17:16:55 +0300	[thread overview]
Message-ID: <201807221416.w6MEGtDs021149@skeeve.com> (raw)

Hi All.

I have (mostly) revived Doug McIlroy's C++ regular expression parsing
library.  I gratefully acknowledge and thank him for allowing me to
publish the code and for his help in finding all the bits and pieces.

It's available at https://github.com/arnoldrobbins/mcilroy-regex .
The main things I've done are to gather all the bits and pieces, rename files
to have a .cpp extension, and get everything to compile using current g++
and standard make.

I'm at the point where I could use some help. The various tests
do not all run successfully. 

1. make retest - a number of tests fail
2. ./tesgrep.sh - a number of tests fail
3. ./testsed.sh - tests fail with core dumps

Looking briefly, some of the code in sed plays C games, casting various
things arouond to pointers of different types and dereferencing them;
these things tend to cause trouble in C++.

I'm hopeful that more eyes on this code will help it come back to life
more quickly.  Any and all help will be appreciated.

Thanks,

Arnold

P.S. Let's not start a flame war about C vs. C++ etc. etc.  If you can
help, please just dive in. Otherwise, just go, "wow, neat work" and
move on to something else. :-) Thanks.

             reply	other threads:[~2018-07-22 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-22 14:16 Arnold Robbins [this message]
2018-07-28 22:31 Doug McIlroy
2018-07-29  6:02 ` arnold
2018-08-01  4:15   ` Larry McVoy

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=201807221416.w6MEGtDs021149@skeeve.com \
    --to=arnold@skeeve.com \
    --cc=tuhs@tuhs.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).