From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] Regular Expressions
Date: Fri, 31 Jul 2020 20:00:23 -0400 (EDT) [thread overview]
Message-ID: <20200801000023.3CF0818C0C0@mercury.lcs.mit.edu> (raw)
> From: Will Senn
> I don't really understand how they work.
> ...
> maybe the way to understand the unix regex lies in a careful
> investigation into how it is implemented
I'm not sure what I did, but it wasn't the latter, since I have no idea how
they are done!
I just mentally break the regex search string up into substrings (I use them
most in Epsilon, which has syntax to do substrings of search strings, which
helps a lot); past that, I think it's just using them and getting used to
them.
> an IBM 7094 (whatever that is)
IBM's last 36-bit scientific mainframe before the System/360's. CTSS (which
DMR held out as the ancestor of Unix) ran on 7094's.
Noel
next reply other threads:[~2020-08-01 0:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 0:00 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-02 4:59 Rudi Blom
2020-08-01 21:12 Doug McIlroy
2020-08-09 23:44 ` Dave Horsfall
2020-08-10 0:50 ` Rob Pike
2020-07-31 22:57 Will Senn
2020-08-01 0:01 ` Bakul Shah
2020-08-01 0:36 ` Rob Pike
2020-08-01 0:53 ` John P. Linderman
2020-08-01 1:31 ` Bakul Shah
2020-08-01 1:39 ` Larry McVoy
2020-08-01 2:33 ` Will Senn
2020-08-01 2:50 ` Rich Morin
2020-08-01 3:01 ` Larry McVoy
2020-08-01 3:07 ` Will Senn
2020-08-01 4:31 ` Earl Baugh
2020-08-01 4:53 ` ron minnich
2020-08-01 5:48 ` Andrew Hume
2020-08-01 13:31 ` Richard Salz
2020-08-01 13:43 ` Andrew Hume
2020-08-02 0:45 ` Christopher Browne
2020-08-09 1:00 ` Dave Horsfall
2020-08-09 1:15 ` Nelson H. F. Beebe
2020-08-09 23:53 ` Dave Horsfall
2020-08-10 1:38 ` John Cowan
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=20200801000023.3CF0818C0C0@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=tuhs@minnie.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).