From b248654cba0d6c5ae213882837140358f92bab1c Mon Sep 17 00:00:00 2001 From: dos-reis Date: Sun, 9 May 2010 15:57:28 +0000 Subject: * boot/tokens.boot: Don't rename 'cons'. * interp/msg.boot: Remove uses of cons. * interp/postpar.boot: Likewise. * interp/types.boot: Likewise. --- STYLES | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) (limited to 'STYLES') diff --git a/STYLES b/STYLES index 49756f93..0d9c15d9 100644 --- a/STYLES +++ b/STYLES @@ -1,13 +1,13 @@ Styles for Boot Codes --------------------- - The core of the OpenAxiom system is mostly written Boot. A long + The core of the OpenAxiom system is mostly written in Boot. A long time ago, Boot was essentially a Lisp DSL with a much more palatable -syntax geared specifically for writing readable codes. As such it +syntax geared specifically toward writing readable codes. As such it tended to have lots of Lispism in it. There days, Boot is no longer `just a syntactic sugar over Lisp', -even currently, we essentially translate to Lisp. Boot is a +even when we essentially translate to Lisp. Boot is a programming language in of its own. In fact, we would like to remove Lispism from Boot codes. The `rules' below are suggestions (or guidelines) for writing `good Boot codes'. @@ -31,9 +31,11 @@ guidelines) for writing `good Boot codes'. -- GOOD -- first form in '(Mapping Record) => -- ... + form.first := '%LET -- BAD -- CAR form in '(Mapping Record) => -- ... + RPLACA(form,'%LET) * Don't use `null' to test for Boolean values, use `not' @@ -45,4 +47,11 @@ guidelines) for writing `good Boot codes'. -- BAD -- null $monitorNewworld => ... +* Use idiomatic Boot constructs + Example: + -- GOOD -- + vars := [var,:vars] + + -- BAD -- + vars := CONS(var,vars) -- cgit v1.2.3