diff options
author | Kaz Kylheku <kaz@kylheku.com> | 2013-07-13 16:34:36 -0700 |
---|---|---|
committer | Kaz Kylheku <kaz@kylheku.com> | 2013-07-13 16:34:36 -0700 |
commit | dbbc63a5ad6b518a7c9114c448c3f1b0d7cda6fb (patch) | |
tree | 1e8dbe36097cafa794b5131f2f8183592bc7267e /txr.1 | |
parent | 354b6cf42c3dad99aed8d7ed49454e69b5460824 (diff) | |
download | txr-dbbc63a5ad6b518a7c9114c448c3f1b0d7cda6fb.tar.gz txr-dbbc63a5ad6b518a7c9114c448c3f1b0d7cda6fb.tar.bz2 txr-dbbc63a5ad6b518a7c9114c448c3f1b0d7cda6fb.zip |
Version 67
txr.1: Documented line continuation for string literals,
supported since Version 38 but not clarified properly.
RELNOTES: Updated.
Diffstat (limited to 'txr.1')
-rw-r--r-- | txr.1 | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -1089,6 +1089,14 @@ delimiter disappears. To write a literal semicolon immediately after a hex or octal escape, write two semicolons, the first of which will be interpreted as a delimiter. Thus, "\ex21;;" represents "!;". +If the line ends in the middle of a literal, it is an error, unless the +last character is a backslash. This backslash is a special escape which does +not denote a character; rather, it indicates that the string literal continues +on the next line. Leading whitespace in the following line is deleted, and +does not constitute part of the string literal, which allows for indentation. +The escape sequence "\e " (backslash space) can be used to encode a +significant space. + .SS String Quasiliterals Quasiliterals are similar to string literals, except that they may |