Mercurial > hg > BCS
comparison CR_preface.txt @ 30:b23d34ac6765
Sunday
| author | Henry Thompson <ht@markup.co.uk> |
|---|---|
| date | Sun, 03 Nov 2024 09:48:11 -0500 |
| parents | 7688b405c09f |
| children | 8d2fbd093ff3 |
comparison
equal
deleted
inserted
replaced
| 29:0e63562b01e6 | 30:b23d34ac6765 |
|---|---|
| 181 already | 181 already |
| 182 | 182 |
| 183 [HST what about program correctness, specification languages ? etc.] | 183 [HST what about program correctness, specification languages ? etc.] |
| 184 | 184 |
| 185 [Chapter 7?] | 185 [Chapter 7?] |
| 186 | |
| 187 [HST should read the Press's thoughts about what needs to happen in | |
| 188 the preface] | |
| 189 | |
| 190 The gap between computer science and and programming practice is | |
| 191 well-known, embarrassing but rarely foregrounded. | |
| 192 | |
| 193 The vocabulary point is easy to state. | |
| 194 | |
| 195 Barwise foundered on different understandings of binding a variable. | |
| 196 | |
| 197 That the vocabulary issue is of huge importance needs "a clarion | |
| 198 statement". This is foundational work, so I can't define my terms. | |
| 199 | |
| 200 "I don't believe in definitions" | |
| 201 | |
| 202 "Look, this kind of paper that I write should be read more like novel | |
| 203 than like a manual. What things mean will gradually take shape" | |
| 204 | |
| 205 Engender confidence that what you're about to read will make sense by | |
| 206 the end/in due course/by-and-by. | |
| 207 | |
| 208 Vocabulary point is several points: | |
| 209 1) Points will be expressed using a vocabulary which is a term | |
| 210 of art for someone/drawn from someone's technical vocabulary, perhaps not you | |
| 211 2) Also, not necessarily the term of art you use for it; | |
| 212 Indeed it may be an ordinary word of English, so you may not | |
| 213 realise that a term of art has gone by. | |
| 214 3) There may not be terms in _any_ technical vocabulary that do what | |
| 215 I need here | |
| 216 | |
| 186 ------------ | 217 ------------ |
| 187 Foundations of/Philosophy of Computation | 218 Foundations of/Philosophy of Computation |
| 188 | 219 |
| 189 Lisp was 'broken', 2-Lisp was a flawed attempt to fix it, 3-Lisp takes | 220 Lisp was 'broken', 2-Lisp was a flawed attempt to fix it, 3-Lisp takes |
| 190 us in to new territory. | 221 us in to new territory. |