diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/breaking_rules.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/breaking_rules.md b/doc/breaking_rules.md index d9c499b..947ca80 100644 --- a/doc/breaking_rules.md +++ b/doc/breaking_rules.md @@ -1,6 +1,6 @@ title: Breaking the Rules: Refining Prototypes Into Products author: Darren Bane -copyright: 2021 Darren Bane, CC BY-SA +copyright: 2020-21 Darren Bane, CC BY-SA # Abstract @@ -50,7 +50,7 @@ without earning money. ## Design Decisions -The programming language chosen is ISLisp +The programming language chosen is ISLisp. Reasons for this decision include: * Contrary to a lot of other languages, Lisp is fairly paradigm-agnostic. @@ -64,7 +64,7 @@ Reasons for this decision include: Detailed implementations, libraries, etc. are as follows: -* The EISL compiler. +* The Easy-ISLisp interpreter/compiler. * Avoid multi-threading at this stage, event-driven should do the job. * Not sure if this is relevant for a prototype, but you could do simple multi-user @@ -85,7 +85,7 @@ Standard UNIX libraries like curses, catgets, xdr and dbm can still be used from Even though this is a prototype, attention should be paid to basic craftsmanship. * Divide the system conceptually into packages. - This can be as simple as "section headers" with lots of semicolons. + This can start from just "section headers" with lots of semicolons. * Write comments for at least each public fun, class and package. There are guidelines in the Elisp manual, but for now one sentence will suffice. * Dynamically |