diff options
| author | Marshall Lochbaum <mwlochbaum@gmail.com> | 2020-10-03 16:38:35 -0400 |
|---|---|---|
| committer | Marshall Lochbaum <mwlochbaum@gmail.com> | 2020-10-03 16:38:35 -0400 |
| commit | 673de1c627a2046123e1693e9e6508399a028508 (patch) | |
| tree | 86303316523319eeebcf0e0c52a2be781089c286 /docs/implementation/codfns.html | |
| parent | 8846e63a6f1fe51ee9a68dc511cc6fcdbf54efa6 (diff) | |
Write files directly from md.bqn, not gendocs (removes trailing empty lines)
Diffstat (limited to 'docs/implementation/codfns.html')
| -rw-r--r-- | docs/implementation/codfns.html | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/docs/implementation/codfns.html b/docs/implementation/codfns.html index 1cb63eaf..9b9c14f6 100644 --- a/docs/implementation/codfns.html +++ b/docs/implementation/codfns.html @@ -22,4 +22,3 @@ </ul> <p>Aaron advocates the almost complete separation of code from comments (thesis) in addition to his very terse style as a general programming methodology. I think these choices are good for rapid development but not for maintainance and explaining the code to other developers. I will write separate long-form material on implementation, but will start expanding the source code and adding comments, mainly to explain the meaning of variables whose definitions are not instantly obvious.</p> <p>Co-dfns does not check for compilation errors. BQN should have complete error checking, and good error messages. Maybe it can even give better error diagnosis than sequential compilers in some cases by examining the input as a whole to find the most likely cause of the mistake. Particularly for web distribution it may still make sense to have a version of the compiler that doesn't check for errors; this should be possible simply by setting a configuration parameter when compiling the compiler.</p> - |