Update this text for general subscripting as well.

chapters/operatorsandexpressions.tex

@@ -118,16 +118,19 @@ \section{Operator Precedence and Associativity}\label{operator-precedence-and-as
 \end{lstlisting}
 These are some valid as well as invalid ways to using postfix array index and postfix access:
 \begin{lstlisting}[language=modelica]
-a[3].x[2] // OK: Component reference of type Real
-a[3].x    // OK: Component reference of type Real[2]
-a.x[2]    // OK: Component reference of type Real[3]
-a.x       // OK: Component reference of type Real[3, 2]
-(a.x)[2]  // Error: Invalid use of parentheses
-a[3]      // OK: Component reference of type R
-(a[3]).x  // Error: Invalid use of parentheses
+a[3].x[2]   // OK: Component reference of type Real
+a[3].x      // OK: Component reference of type Real[2]
+a.x[2]      // OK: Component reference of type Real[3]
+a.x[2, :]   // Error.
+a.x         // OK: Component reference of type Real[3, 2]
+(a.x)[2]    // OK: Component reference of type Real[2] - same as a[2].x[:]
+(a.x)[2, :] // OK: Component reference of type Real[2] - same as a[2].x[:]
+a[3]        // OK: Component reference of type R
+(a[3]).x    // Error: Invalid use of parentheses
 \end{lstlisting}
 The relation between \lstinline!a.x!, \lstinline!a.x[2]!, and \lstinline!(a.x)[2]! illustrates the effect of giving higher precedence to array index than postfix access.
-Had the precedence been equal, this would have changed the meaning of \lstinline!a.x[2]! to the same thing that \lstinline!(a.x)[2]! tries to express, being a component reference of type \lstinline!Real[2]!.
+Had the precedence been equal, this would have changed the meaning of \lstinline!a.x[2]! to the same thing that \lstinline!(a.x)[2]! expresses, being a component reference of type \lstinline!Real[2]!.
+Note that \lstinline!(a.x)[2]! was illegal in version 3.6 and earlier.
 \end{example}
 
 \begin{example}