Choose a more suitable example for the operator precedence mis-parsing

example.

diff --git a/doc/src/sgml/syntax.sgml b/doc/src/sgml/syntax.sgml
index cd463488fb6fa08a894facab419ff34477b01c11..181d113a415dc232d59267a19c4160c421e97efd 100644 (file)
--- a/doc/src/sgml/syntax.sgml
+++ b/doc/src/sgml/syntax.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/syntax.sgml,v 1.39 2001/02/10 07:08:44 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/syntax.sgml,v 1.40 2001/02/24 18:09:51 petere Exp $
 -->
 
 <chapter id="sql-syntax">
@@ -905,17 +905,17 @@ sqrt(2)
     you will sometimes need to add parentheses when using combinations
     of binary and unary operators.  For instance
 <programlisting>
-SELECT 5 ! ~ 6;
+SELECT 5 ! + 6;
 </programlisting>
    will be parsed as
 <programlisting>
-SELECT 5 ! (~ 6);
+SELECT 5 ! (+ 6);
 </programlisting>
-    because the parser has no idea --- until it's too late --- that
-    <token>!</token> is defined as a postfix operator not an infix one.
+    because the parser has no idea -- until it is too late -- that
+    <token>!</token> is defined as a postfix operator, not an infix one.
     To get the desired behavior in this case, you must write
 <programlisting>
-SELECT (5 !) ~ 6;
+SELECT (5 !) + 6;
 </programlisting>
     This is the price one pays for extensibility.
    </para>