From: Adam Thornton <athornton@gmail.com>
To: Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] [TUHS] Book Recommendation [ reallly inscrutable languages ]
Date: Wed, 17 Nov 2021 15:31:06 -0700 [thread overview]
Message-ID: <CAP2nic1NririVVsoJLb037YU0qZpucBphngqVkoP9mP2_svC_g@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgyY1eW8O=ky5_88kP7Z0EKC1E2TjDyi4tKkzG0hfooSHw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 564 bytes --]
On Wed, Nov 17, 2021 at 3:24 PM Rob Pike <robpike@gmail.com> wrote:
> Perl certainly had its detractors, but for a few years there it was the
> lingua franca of system administration.
>
It's still what I reach for first when I need to write a state machine that
processes a file made up of lines with some--or some set of--structures.
The integration of regexps is far, far, far superior to what Python can do,
and I adore the while(<>) construct. Maintaining other people's Perl
usually sucks, but it's a very easy way to solve your own little problems.
Adam
[-- Attachment #1.2: Type: text/html, Size: 959 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next parent reply other threads:[~2021-11-17 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKH6PiXinxBQGRqoeGMcG9CwTA5BNeU-LY164f-ZLYA4obsyuA@mail.gmail.com>
[not found] ` <202111161754.1AGHsGsN929905@darkstar.fourwinds.com>
[not found] ` <50F3E958-F0A4-4895-B1BC-41A2644A074A@oclsc.org>
[not found] ` <CAGGBd_rRtKF33gUqEvSAc2nD2rpvyYpNY6MfWCnJtEPd2nWbJA@mail.gmail.com>
[not found] ` <CANCZdfp65G_MZRiAQ3pBVW5UCBjhoDk-wu8CLNnX7j4V-9B16g@mail.gmail.com>
[not found] ` <CAEoi9W7EerqquxroDqzaDPeZ03UEcKtC3bXPvyYtUy_8t-pXxQ@mail.gmail.com>
[not found] ` <CAKzdPgyY1eW8O=ky5_88kP7Z0EKC1E2TjDyi4tKkzG0hfooSHw@mail.gmail.com>
2021-11-17 22:31 ` Adam Thornton [this message]
2021-11-17 22:46 ` Bakul Shah
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=CAP2nic1NririVVsoJLb037YU0qZpucBphngqVkoP9mP2_svC_g@mail.gmail.com \
--to=athornton@gmail.com \
--cc=coff@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).