Some improvements to the description
svn: r17193
This commit is contained in:
parent
b5114a14c1
commit
49df9502a4
|
@ -136,13 +136,14 @@ In some cases, the reader functions read the whole file, so there is
|
|||
no need to iterate them (e.g., Scribble's @scheme[read-inside] and
|
||||
@scheme[read-syntax-inside]). In these cases you can specify
|
||||
@scheme[#:whole-body-readers?] as @scheme[#t] --- the readers are
|
||||
expected to return a list of expressions in this case. If those
|
||||
reader functions return a list with a single expression that begins
|
||||
with @scheme[#%module-begin], then the @scheme[syntax/module-reader]
|
||||
language will not inappropriately add another. This is to be
|
||||
backwards-compatible with older code, and adding @scheme[#%module-begin]
|
||||
in the reader functions or in the function specified by @scheme[#:wrapper1]
|
||||
should be considered deprecated behavior.
|
||||
expected to return a list of expressions in this case.
|
||||
|
||||
[If such whole-body reader functions return a list with a single
|
||||
expression that begins with @scheme[#%module-begin], then the
|
||||
@scheme[syntax/module-reader] language will not inappropriately add
|
||||
another. This for backwards-compatibility with older code: having a
|
||||
whole-body reader functions or wrapper functions that return a
|
||||
@scheme[#%module-begin]-wrapped body is deprectaed.]
|
||||
|
||||
In addition, the two wrappers can return a different value than the
|
||||
wrapped function. This introduces two more customization points for
|
||||
|
|
Loading…
Reference in New Issue
Block a user