diff options
| -rw-r--r-- | bitmap.lsp | 1 | ||||
| -rw-r--r-- | doc/breaking_rules.md | 8 |
2 files changed, 5 insertions, 4 deletions
diff --git a/bitmap.lsp b/bitmap.lsp index 059c5cb..e4cdea3 100644 --- a/bitmap.lsp +++ b/bitmap.lsp @@ -1,4 +1,5 @@ ;;; Bitmap +;;; This could be extended to a general drawing interface, but for now it's probably better to use Tk's canvas. (defconstant +black+ 0) (defconstant +white+ #xFFFFFF) diff --git a/doc/breaking_rules.md b/doc/breaking_rules.md index c0f3272..0a88e01 100644 --- a/doc/breaking_rules.md +++ b/doc/breaking_rules.md @@ -90,6 +90,9 @@ The following technology is recommended: * The SBCL compiler. * ltk for the view layer. +For simple multi-user, +use the IRCv3 bots (nickserv, chanserv) and IRCCloud or similar. + The following is probably the most work that makes sense without earning money. @@ -124,9 +127,6 @@ I don't want to maintain my own. DbC would be another nice-to-have, but I settle for `(declare`. -Could do simple multi-user, -using the IRCv3 bots (nickserv, chanserv) and IRCCloud or similar - # Refinement to Production-Quality First, software at the level of the previous section is quite usable. @@ -172,7 +172,7 @@ bane 2008 However, some of this documentation is better in the source code: * The summary of functions should be taken care of by having the public functions and classes commented. -* The formal requirement for function behaviour can be donw with +* The formal requirement for function behaviour can be done with tables with Basic English \.[ basic english |