Post #1782104
2026-04-22 07:55 UTC
@screwlisp The Java book then has a design for (but no impl details) a GUI search engine with WAY too much database of its own, & a summary of Go4's Design Patterns.
The CLU book has program verification, which is mathematically impossible (see Gödel), but at least it's not repeating a better book.
They both go into waterfall design specificationm, apparently in a void or vast organization like IBM where developer time doesn't exist. It's like YT's Mom's job is to implement this stuff.
Replies (1)
-
@screwlisp@gamerplus.org 2026-04-23 01:13
@mdhughes While on very many painkillers, everything came to make sense to me. Before procedural abstraction, they develop the gist of their modules as requires assertion BODY effects assertion (+ modifies assertion) on the hypothesis that a user of a module is expected to ignore the implementation details of bodies for given requires/effects assertions. In my conditions shindig, I am developing instead conditions - LHS handler bodies restarts - RHS bodies But insisting bodies be in ACL2 FOL