summary refs log tree commit diff stats
path: root/doc/manual
diff options
context:
space:
mode:
authorAraq <rumpf_a@web.de>2015-09-10 08:53:58 +0200
committerAraq <rumpf_a@web.de>2015-09-10 10:50:29 +0200
commitd7a472743b6d3e7c0062621d0b861d20edf89663 (patch)
tree931e0ac1d5197e7bced1677e6633f48c803a027b /doc/manual
parentffe51966b9a424a55a0a6c5ccac37fe0ced3709f (diff)
downloadNim-d7a472743b6d3e7c0062621d0b861d20edf89663.tar.gz
fixes #2559
Diffstat (limited to 'doc/manual')
-rw-r--r--doc/manual/syntax.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/manual/syntax.txt b/doc/manual/syntax.txt
index 99af15948..c444a3995 100644
--- a/doc/manual/syntax.txt
+++ b/doc/manual/syntax.txt
@@ -68,13 +68,13 @@ Strong spaces
 -------------
 
 The number of spaces preceding a non-keyword operator affects precedence
-if the experimental parser directive ``#!strongSpaces`` is used. Indentation
+if the experimental parser directive ``#?strongSpaces`` is used. Indentation
 is not used to determine the number of spaces. If 2 or more operators have the
 same number of preceding spaces the precedence table applies, so ``1 + 3 * 4``
 is still parsed as ``1 + (3 * 4)``, but ``1+3 * 4`` is parsed as ``(1+3) * 4``:
 
 .. code-block:: nim
-  #! strongSpaces
+  #? strongSpaces
   if foo+4 * 4 == 8  and  b&c | 9  ++
       bar:
     echo ""
@@ -86,7 +86,7 @@ Furthermore whether an operator is used a prefix operator is affected by the
 number of spaces:
 
 .. code-block:: nim
-  #! strongSpaces
+  #? strongSpaces
   echo $foo
   # is parsed as
   echo($foo)
@@ -95,7 +95,7 @@ This also affects whether ``[]``, ``{}``, ``()`` are parsed as constructors
 or as accessors:
 
 .. code-block:: nim
-  #! strongSpaces
+  #? strongSpaces
   echo (1,2)
   # is parsed as
   echo((1,2))