From: Ralph Corderoy <ralph@inputplus.co.uk>
To: tuhs@tuhs.org
Cc: will.senn@gmail.com, mrochkind@gmail.com
Subject: [TUHS] Re: regex early discussions
Date: Mon, 04 Mar 2024 12:05:23 +0000 [thread overview]
Message-ID: <20240304120523.219C01FAA1@orac.inputplus.co.uk> (raw)
In-Reply-To: <202403040725.4247P73R004962@freefriends.org>
Hi Arnold,
> I learned regular expressions from Kernighan & Plauger's book
> "Software Tools". I was exposed to that book, Unix (v6 on a PDP-11)
> and C programming (via K&R's book) all at the same time. This was in
> the fall of 1980.
An excellent book. What I think you've not mentioned is that it
implements regular expressions. Being inside the black box can aid
understanding, including the performance of the matcher and the way the
regexp is best written for a particular matcher.
Kernighan and Pike's ‘The practice of programming’ also briefly
implements some regexp functionality when talking about the power of
notation.
--
Cheers, Ralph.
next prev parent reply other threads:[~2024-03-04 12:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 1:30 [TUHS] " Will Senn
2024-03-04 2:03 ` [TUHS] " Marc Rochkind
2024-03-04 3:38 ` Larry McVoy
2024-03-04 4:18 ` Rich Salz
2024-03-04 7:51 ` Alec Muffett
2024-03-04 8:17 ` Rob Pike
2024-03-04 8:43 ` Alec Muffett
2024-03-04 14:25 ` Jan Schaumann via TUHS
2024-03-04 10:21 ` Bakul Shah via TUHS
2024-03-04 14:34 ` Larry McVoy
2024-03-04 7:10 ` Otto Moerbeek via TUHS
2024-03-04 7:19 ` Dave Long
2024-03-04 7:25 ` arnold
2024-03-04 12:05 ` Ralph Corderoy [this message]
2024-03-04 13:01 ` arnold
2024-03-04 7:25 ` Otto Moerbeek via TUHS
2024-03-04 12:00 ` Peter Weinberger (温博格) via TUHS
2024-03-04 17:05 ` Will Senn
2024-03-04 18:43 ` Rich Salz
2024-03-04 20:57 ` Bakul Shah via TUHS
2024-03-04 21:05 ` Steffen Nurpmeso
2024-03-04 13:17 ` Alan D. Salewski
2024-03-04 16:57 ` Clem Cole
2024-03-04 18:38 ` Phil Budne
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=20240304120523.219C01FAA1@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--cc=mrochkind@gmail.com \
--cc=tuhs@tuhs.org \
--cc=will.senn@gmail.com \
/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).