Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: Clem Cole <clemc@ccc.com>, Lars Brinkhoff <lars@nocrew.org>
Cc: coff@tuhs.org
Subject: [COFF] Re: [TUHS] Re: regex early discussions
Date: Tue, 5 Mar 2024 18:59:46 -0600	[thread overview]
Message-ID: <2b6dc37f-f052-4ea0-9774-b40c6994a512@gmail.com> (raw)
In-Reply-To: <CAC20D2MPVUeojRCVLORaymC_ZPX9v7wvf9YbrQx9OsDsFSdjOw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2488 bytes --]

On 3/5/24 10:34 AM, Clem Cole wrote:
> Will had asked -- how did people learn to use reg-ex?  The observation 
> I had made and was bringing forward to the list is that if new user 
> came from a background based on being taught about how to create a 
> pattern match er, and sid person had learned a little about the ideas 
> behind automatons, learn to use reg-ex was not a big deal.  It was 
> only 'astonishing,' and users might need a separate explanation if 
> they started from some other place - particularly if they did not have 
> that same background in core CS theory/they had previously learned a 
> different way with a different set of tools, such as the text editor.
>
> As I understand it, this is how Will came to learn UNIX, so folks like 
> Will needed and appreciated documentation that came from other places. 
> I think that he was asking which documents and what people in the 
> background similar to him had chosen to use to learn how to use the 
> UNIX toolkit.
>
>
> Clem
>
Yup. I was curious about exactly that and the answers fit the bill 
nicely. I knew that Ritchie & co. were mathy cs types, but it didn't 
occur to me that the rest of the unix folks were, as well. A little 
reflection and it became somewhat obvious. Sure, there were plenty of 
exceptions, but then, they had mathy cs types to lean on. Coming at it 
from the new millennium, it's hard to grok the early days, or recreate 
the aha moments. I'm just using Unix explorations as motivations for 
deeper study of CS stuff that interest me, personally. When I picked up 
the AWK book the other day, regex popped out at me as a deficiency 
(sure, I use them all the time, but mastery... not even close... a lot 
of the time, it's like magic...) so, rather than just start coding up a 
bunch of regexes, I thought I would find out a bit more about their 
genesis - not the research that led to their discovery or perfection (I 
have no mathy interest), but rather how they came into common use (the 
pragmatics, as it were). This led to me asking about the gestalt of the 
60's / 70's and suchlike. For me, this is a bit like virtual reality, 
where I can immerse myself in what it might have been like and how it 
might have unfolded while tooling around like it is 1969 all over again. 
Thankfully, for a lot of y'all it's lived history and by willingly 
sharing so freely, you enrich the real-feel of the simulation :).

Later,

Will




[-- Attachment #2: Type: text/html, Size: 4213 bytes --]

  reply	other threads:[~2024-03-06  0:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <13abd764-984a-4c9f-8e3e-b1eb7c624692@gmail.com>
     [not found] ` <CAC20D2MFY4g+j+e3OUOLgZtcgnYKu93ENjkG80cH59fr5n44bQ@mail.gmail.com>
2024-03-04 20:27   ` Lars Brinkhoff
2024-03-04 20:53     ` Clem Cole
2024-03-05  6:49       ` Lars Brinkhoff
2024-03-05 16:34         ` Clem Cole
2024-03-06  0:59           ` Will Senn [this message]
2024-03-05 19:30 Noel Chiappa

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=2b6dc37f-f052-4ea0-9774-b40c6994a512@gmail.com \
    --to=will.senn@gmail.com \
    --cc=clemc@ccc.com \
    --cc=coff@tuhs.org \
    --cc=lars@nocrew.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).