|
From: | Martin Dorey |
Subject: | Re: [PATCH 1/2] Trivial correction on document |
Date: | Wed, 21 Jun 2017 05:38:01 +0000 |
My native English speaker intuition says that "if it were" and "if it was" are both available there. https://english.stackexchange.com/a/146382 cites Huddleston and Pullum's grammar in agreement.
Other answers suggest the "were" form is getting rarer, so maybe it's a good idea to change it, even though it was right before.
I just couldn't see the "that that" problem with a line break in between them on my phone screen until a non-native speaker pointed it out. Doh.
---
doc/make.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/make.texi b/doc/make.texi index dfa4454..343927b 100644 --- a/doc/make.texi +++ b/doc/make.texi @@ -1831,7 +1831,7 @@ more recent than it. @item How to update the file @file{foo.o}: by running @code{cc} as stated. The recipe does not explicitly mention @file{defs.h}, but we presume -that @file{foo.c} includes it, and that that is why @file{defs.h} was +that @file{foo.c} includes it, and that is why @file{defs.h} was added to the prerequisites. @end itemize @end ifnottex @@ -10861,7 +10861,7 @@ into a Guile string and provided as the result of the procedure. @item gmk-eval @findex gmk-eval This procedure takes a single argument which is converted into a -string. The string is evaluated by @code{make} as if it were a +string. The string is evaluated by @code{make} as if it was a makefile. This is the same capability available via the @code{eval} function (@pxref{Eval Function}). The result of the @code{gmk-eval} procedure is always the empty string. -- 2.1.0 _______________________________________________ Bug-make mailing list address@hidden https://na01.safelinks.protection.outlook.com/?url=""> |
[Prev in Thread] | Current Thread | [Next in Thread] |