summary refs log tree commit diff stats
path: root/doc/manual
diff options
context:
space:
mode:
authorAndreas Rumpf <rumpf_a@web.de>2016-01-17 20:29:50 +0100
committerAndreas Rumpf <rumpf_a@web.de>2016-01-17 20:29:50 +0100
commita4aeb6fbecaabed2ae14c2405d9caa6699aec43e (patch)
treefbef1670fdc0d5eec0ddb555f1e16521406a4ab4 /doc/manual
parent2e71bd50b26e6165121a3076f7dc70175e9f1f55 (diff)
downloadNim-a4aeb6fbecaabed2ae14c2405d9caa6699aec43e.tar.gz
implements final version of multiline comments
Diffstat (limited to 'doc/manual')
-rw-r--r--doc/manual/lexing.txt23
1 files changed, 7 insertions, 16 deletions
diff --git a/doc/manual/lexing.txt b/doc/manual/lexing.txt
index a5c3dfd6d..7655964ee 100644
--- a/doc/manual/lexing.txt
+++ b/doc/manual/lexing.txt
@@ -78,33 +78,24 @@ They look like:
 .. code-block:: nim
   #[Comment here.
   Multiple lines
-  are not a problem.]
+  are not a problem.]#
 
-.. code-block:: nim
-  #[[comment here]]
-
-.. code-block:: nim
-  #[[[comment here]]]
-
-.. code-block:: nim
-  #[[[[comment here]]]]
-
-The number of opening brackets must match the number of closing brackets
-but they do not nest in the traditional sense:
+Multiline comments support nesting:
 
 .. code-block:: nim
   # Does not comment out 'p' properly:
-  #[
+  #[  #[ Multiline comment in already
+     commented out code. ]#
   proc p[T](x: T) = discard
-  ]
+  ]#
 
-Multiline documentation comments look like:
+Multiline documentation comments look like and support nesting too:
 
 .. code-block:: nim
   proc foo =
     ##[Long documentation comment
     here.
-    ]
+    ]##
 
 
 Identifiers & Keywords