# HG changeset patch
# User Henry Thompson <ht@markup.co.uk>
# Date 1730645291 18000
# Node ID b23d34ac6765f4bc6845bec6f0ed7d97289ca638
# Parent  0e63562b01e6e0fb9cd00a025b101c38dc0d60ac
Sunday

diff -r 0e63562b01e6 -r b23d34ac6765 CR_preface.txt
--- a/CR_preface.txt	Sat Nov 02 22:32:27 2024 +0000
+++ b/CR_preface.txt	Sun Nov 03 09:48:11 2024 -0500
@@ -183,6 +183,37 @@
 [HST what about program correctness, specification languages ? etc.]
 
 [Chapter 7?]
+
+[HST should read the Press's thoughts about what needs to happen in
+ the preface]
+
+The gap between computer science and and programming practice is
+well-known, embarrassing  but rarely foregrounded.
+
+The vocabulary point is easy to state.
+
+Barwise foundered on different understandings of binding a variable.
+
+That the vocabulary issue is of huge importance needs "a clarion
+statement".  This is foundational work, so I can't define my terms.
+
+"I don't believe in definitions"
+
+"Look, this kind of paper that I write should be read more like novel
+than like a manual.  What things mean will gradually take shape"
+
+Engender confidence that what you're about to read will make sense by
+the end/in due course/by-and-by.
+
+Vocabulary point is several points: 
+ 1) Points will be expressed using a vocabulary which is a term
+     of art for someone/drawn from someone's technical vocabulary, perhaps not you
+ 2) Also, not necessarily the term of art you use for it; 
+    Indeed it may be an ordinary word of English, so you may not
+    realise that a term of art has gone by.
+ 3) There may not be terms in _any_ technical vocabulary that do what
+    I need here
+
 ------------
 Foundations of/Philosophy of Computation