From: Larry McVoy <lm@mcvoy.com>
To: segaloco <segaloco@protonmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Make(1) Historical Behavior (was Cool talk on Unix and Sendmail history, by Eric Allman)
Date: Wed, 2 Aug 2023 17:55:46 -0700 [thread overview]
Message-ID: <20230803005546.GB12652@mcvoy.com> (raw)
In-Reply-To: <_KiSAucAzsj36hyLVdRHwFxz29dzdQpEBVnubkrKkP8_dMy0gmD2VQ3Bi9c8W5zq1v91VouPvLz-6t0yBJtNGYNUw2mGV7crtEAZwtBthus=@protonmail.com>
On Thu, Aug 03, 2023 at 12:01:16AM +0000, segaloco via TUHS wrote:
> > And I think even V7 make supported what you described, as well as implicit rules for compiling .c into a .o or into a binary.
> >
> > Warner Losh
>
> You're right, I just tried it out. Been avoiding that pattern for years because I swear some make implementation I used at one point was very unhappy with that, but if V7 does it, then whatever implementation that was is probably not what I want to be using anyway.
For years, I carried around some early version of make source. Maybe Sys
III make? It wasn't fancy but it behaved how I understood it should
behave and all the other makes, ESPECIALLY gnu make, were adding features
like crazy and, while cool, they were not portable.
I really like stuff that Just Works (tm) and really early make felt like
that.
I'm a dinosaur, there was a saying at my company "Oh, that was invented
after 1980, Larry won't let you use that" which was mostly correct but
I let you use stuff like mmap(). Also not that portable but oh so useful
when it worked.
--lm
prev parent reply other threads:[~2023-08-03 0:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 0:01 segaloco via TUHS
2023-08-03 0:55 ` Larry McVoy [this message]
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=20230803005546.GB12652@mcvoy.com \
--to=lm@mcvoy.com \
--cc=segaloco@protonmail.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).