summary refs log tree commit diff stats
path: root/doc
diff options
context:
space:
mode:
authorAndreas Rumpf <rumpf_a@web.de>2018-05-01 09:38:17 +0200
committerAndreas Rumpf <rumpf_a@web.de>2018-05-01 09:38:17 +0200
commitd62fe7d5384139ad55277c108bf88c105a3c5d30 (patch)
tree16cf5d0a4eee668a94c991b41418dd373626b489 /doc
parent6853793ae993a58a3462771a6f32a043512bc943 (diff)
downloadNim-d62fe7d5384139ad55277c108bf88c105a3c5d30.tar.gz
update the documentation
Diffstat (limited to 'doc')
-rw-r--r--doc/tut1.rst10
1 files changed, 3 insertions, 7 deletions
diff --git a/doc/tut1.rst b/doc/tut1.rst
index 2dc502fab..f2251c463 100644
--- a/doc/tut1.rst
+++ b/doc/tut1.rst
@@ -944,12 +944,8 @@ String variables are **mutable**, so appending to a string
 is possible, and quite efficient. Strings in Nim are both zero-terminated and have a
 length field. A string's length can be retrieved with the builtin ``len``
 procedure; the length never counts the terminating zero. Accessing the
-terminating zero is not an error and often leads to simpler code:
-
-.. code-block:: nim
-  if s[i] == 'a' and s[i+1] == 'b':
-    # no need to check whether ``i < len(s)``!
-    ...
+terminating zero is an error, it only exists so that a Nim string can be converted
+to a ``cstring`` without doing a copy.
 
 The assignment operator for strings copies the string. You can use the ``&``
 operator to concatenate strings and ``add`` to append to a string.
@@ -960,7 +956,7 @@ enforced. For example, when reading strings from binary files, they are merely
 a sequence of bytes. The index operation ``s[i]`` means the i-th *char* of
 ``s``, not the i-th *unichar*.
 
-String variables are initialized with the empty strings ``""``.
+A string variable is initialized with the empty string ``""``.
 
 
 Integers