Commit 187840b7 authored by Philipp Marek's avatar Philipp Marek

Typos

parent 05f8d916
......@@ -2,7 +2,7 @@ Motivation
The Common Lisp standard describes a lot of facilities for treating code as
data. Unfortunately, it stops short of specifying enough functionality to
allow writing a portable code walker. In addition, some requirements that the
allow writing a portable code walker. In addition, some requirements that
might have been assumed to be implications of the standard are not spelled out
explicitly. As a result, implementations have different behaviour, which
creates more corner cases than necessary for partial code walking
......@@ -50,7 +50,7 @@ declarations as described in CLtL2.
PARSE-MACRO — this symbol names a function for processing macro definitions
like defmacro does as described in CLtL2.
ENCLOSE this symbol names a function for processing an anonynmous function
ENCLOSE — this symbol names a function for processing an anonymous function
definition in a (compile-time) lexical environment as described in CLtL2.
BLOCK-INFORMATION — this symbol names a function that accepts a block name and
......@@ -100,7 +100,7 @@ LEXICAL-ENVIRONMENT — this symbol names a type that includes all possible
non-NIL values of &environment parameter to macros defined via DEFMACRO or
MACROLET. The type SHOULD be as narrow as feasible.
Additionally, implementation MAY provide :CDR-NN-EXPANSIONS in *features*. In
Additionally, implementations MAY provide :CDR-NN-EXPANSIONS in *features*. In
this case, the following constraints SHALL hold.
A compliant implementation SHALL provide macro definitions for all operators
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment