From cb05a7bd98e0c9682a686cd743291923d7ec5d23 Mon Sep 17 00:00:00 2001 From: Avery Pennarun Date: Tue, 18 Sep 2018 13:23:28 -0400 Subject: [PATCH] Nowadays there is a "non-recursive make considered harmful" paper. Of course there is! Let's complete the circle by linking to it, because it links to this project (among many others). --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ee2312c..251915d 100644 --- a/README.md +++ b/README.md @@ -783,8 +783,8 @@ partial picture of what's going on; moreover, each one has to stat() a lot of the same files over again, leading to slowness. That's the thesis of the "considered harmful" paper. -Nobody has written a paper about it, but *non-recursive* -make should also be considered harmful! The problem is Makefiles aren't +It turns out that [non-recursive make should also be considered harmful](https://www.microsoft.com/en-us/research/wp-content/uploads/2016/03/hadrian.pdf). +The problem is Makefiles aren't very "hygienic" or "modular"; if you're not running make recursively, then your one copy of make has to know *everything* about *everything* in your entire project. Every variable in make is global, so every variable defined