Really minor format changes. Unimportant.
This commit is contained in:
parent
ebbbe7192f
commit
5be3a20f9b
|
@ -45,7 +45,7 @@ procedure
|
||||||
string-reduce default construct string --> string
|
string-reduce default construct string --> string
|
||||||
|
|
||||||
Does a "fold-right" on string. The resulting string is
|
Does a "fold-right" on string. The resulting string is
|
||||||
(CONSTRUCT ... (CONSTRUCT STRING[1] (CONSTRUCT STRING[0] DEFAULT)) ...)
|
(CONSTRUCT ... (CONSTRUCT STRING[n-1] (CONSTRUCT STRING[n] DEFAULT)) ...)
|
||||||
Example:
|
Example:
|
||||||
|
|
||||||
(string-reduce "" (lambda (char str)
|
(string-reduce "" (lambda (char str)
|
||||||
|
@ -60,7 +60,7 @@ string-prefix? prefix string --> boolean
|
||||||
string-suffix? suffix string --> boolean
|
string-suffix? suffix string --> boolean
|
||||||
|
|
||||||
Return #t if PREFIX/SUFFIX is a real prefix/suffix of STRING,
|
Return #t if PREFIX/SUFFIX is a real prefix/suffix of STRING,
|
||||||
otherwise return #f. Real prefix/suffix mean that STRING may not be a
|
otherwise return #f. Real prefix/suffix means that STRING may not be a
|
||||||
prefix/suffix of PREFIX/SUFFIX.
|
prefix/suffix of PREFIX/SUFFIX.
|
||||||
|
|
||||||
|
|
||||||
|
|
|
@ -29,7 +29,9 @@ parse-uri uri-string --> (scheme, path, search, frag-id)
|
||||||
Multiple-value return: scheme, path, search, frag-id, in this
|
Multiple-value return: scheme, path, search, frag-id, in this
|
||||||
order. scheme, search and frag-id are either #f or a string. path is a
|
order. scheme, search and frag-id are either #f or a string. path is a
|
||||||
nonempty list of strings. An empty path is a list containing the empty
|
nonempty list of strings. An empty path is a list containing the empty
|
||||||
string. parse-uri tries to be tolerant of the various ways people build broken URIs out there on the Net (so it is not absolutely conform with RFC 1630).
|
string. parse-uri tries to be tolerant of the various ways people
|
||||||
|
build broken URIs out there on the Net (so it is not absolutely
|
||||||
|
conform with RFC 1630).
|
||||||
|
|
||||||
|
|
||||||
procedure
|
procedure
|
||||||
|
|
Loading…
Reference in New Issue