Simple explanation for developers, too?
David A. Wheeler 25 May 2006 19:15 UTC
It might be helpful to give developers a SIMPLE mental model of
how to reason about code indented like this. E.G.:
When writing programs with these rules, the result is:
* You must indent at least one space
* The function name always begins the expression, as usual in Scheme
* The function parameters are the space-separated parameters after the name,
followed by all lines that are one indent level greater
* The list of function parameters ends at a later line that's indented the same or less
--- David A. Wheeler