summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndy Wingo <wingo@pobox.com>2017-05-22 15:40:10 +0200
committerAndy Wingo <wingo@pobox.com>2017-05-22 15:40:10 +0200
commit67b35bba672a40bcc916c6f58cf48b4ef56a8038 (patch)
treeaf7416cac82c8f7eab6f091f91c3b73043612be9
parent1f560bc4b7d1116d678c82f781b2c9259d20c59d (diff)
downloadguile-67b35bba672a40bcc916c6f58cf48b4ef56a8038.tar.gz
Update uri? documentation.
* doc/ref/web.texi (URIs): Update uri? documentation for deprecation removal.
-rw-r--r--doc/ref/web.texi10
1 files changed, 3 insertions, 7 deletions
diff --git a/doc/ref/web.texi b/doc/ref/web.texi
index 7c6a9545e..07da5b64b 100644
--- a/doc/ref/web.texi
+++ b/doc/ref/web.texi
@@ -343,6 +343,9 @@ enforce enforce specific restrictions on the URI-reference. The most
generic URI parser is then @code{string->uri-reference}, and there is
also a parser for when you know that you want a relative-ref.
+Note that @code{uri?} will only return @code{#t} for URI objects that
+have schemes; that is, it rejects relative-refs.
+
@deffn {Scheme Procedure} string->uri-reference string
Parse @var{string} into a URI object, while not requiring a scheme.
Return @code{#f} if the string could not be parsed.
@@ -353,13 +356,6 @@ Parse @var{string} into a URI object, while asserting that no scheme is
present. Return @code{#f} if the string could not be parsed.
@end deffn
-For compatibility reasons, note that @code{uri?} will return @code{#t}
-for all URI objects, even relative-refs. In contrast, @code{build-uri}
-and @code{string->uri} require that the resulting URI not be a
-relative-ref. As a predicate to distinguish relative-refs from proper
-URIs (in the language of RFC 3986), use something like @code{(and
-(uri-reference? @var{x}) (not (relative-ref? @var{x})))}.
-
@node HTTP
@subsection The Hyper-Text Transfer Protocol