(SRFI-1 Searching): In break, note conflict with
binding established by `while'.
This commit is contained in:
parent
9f1af5d96e
commit
3e73b6f9df
1 changed files with 5 additions and 0 deletions
|
|
@ -672,6 +672,11 @@ tail. @code{break} inverts the sense of the predicate.
|
||||||
@code{span!} and @code{break!} are allowed, but not required to modify
|
@code{span!} and @code{break!} are allowed, but not required to modify
|
||||||
the structure of the input list @var{lst} in order to produce the
|
the structure of the input list @var{lst} in order to produce the
|
||||||
result.
|
result.
|
||||||
|
|
||||||
|
Note that the name @code{break} conflicts with the @code{break}
|
||||||
|
binding established by @code{while} (@pxref{while do}). Applications
|
||||||
|
wanting to use @code{break} from within a @code{while} loop will need
|
||||||
|
to make a new define under a different name.
|
||||||
@end deffn
|
@end deffn
|
||||||
|
|
||||||
@deffn {Scheme Procedure} any pred lst1 lst2 @dots{}
|
@deffn {Scheme Procedure} any pred lst1 lst2 @dots{}
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue