summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2018-03-30 10:42:57 -0700
committerKaz Kylheku <kaz@kylheku.com>2018-03-30 10:42:57 -0700
commitfdf176960fee2f2ee2e20c92d1b2d1e3363cf5ce (patch)
tree9ad96f14de1dadd0eb4581b912d04be2f2fc2934
parent8f6422ad7c34d07d7ff81384e789168fa6c10759 (diff)
downloadtxr-fdf176960fee2f2ee2e20c92d1b2d1e3363cf5ce.tar.gz
txr-fdf176960fee2f2ee2e20c92d1b2d1e3363cf5ce.tar.bz2
txr-fdf176960fee2f2ee2e20c92d1b2d1e3363cf5ce.zip
doc: null char in str out stream: incorrect.
* txr.1: The described behavior regarding null bytes output into string output streams is incorrect. In fact they are effectively dropped by the put-char operation. Let's not commit to any specific behavior. Also mention pseudo-null.
-rw-r--r--txr.112
1 files changed, 8 insertions, 4 deletions
diff --git a/txr.1 b/txr.1
index fdf6bc9d..ecfe3219 100644
--- a/txr.1
+++ b/txr.1
@@ -43054,10 +43054,14 @@ The
.code get-string-from-stream
function is used to retrieve the accumulated string.
-If the null character is written to a string output stream, either via
-a character output operation or as a byte operation, the resulting string
-will appear to be prematurely terminated. \*(TX strings cannot contain null
-bytes.
+If the null character is written to a string output stream, the behavior
+is unspecified. \*(TX strings cannot contain null bytes. A the pseudo-null
+character
+.codn #\exDC00 ,
+also notated
+.codn #\epnul ,
+will produce a null byte when converted to UTF-8 and thus serves as an
+effective internal representation of the null character in external data.
.coNP Function @ get-string-from-stream
.synb