[xalan-java] branch xalan-j_xslt3.0 updated: minor changes to comments within one of xalanj src file on this branch

[mu...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mukulg pushed a commit to branch xalan-j_xslt3.0
in repository https://gitbox.apache.org/repos/asf/xalan-java.git


The following commit(s) were added to refs/heads/xalan-j_xslt3.0 by this push:
     new 811b6169 minor changes to comments within one of xalanj src file on this branch
     new c81acf8b Merge pull request #41 from mukulga/xalan-j_xslt3.0_mukul
811b6169 is described below

commit 811b616996111d4920de65f4d7f93bcde43a464d
Author: Mukul Gandhi <ga...@gmail.com>
AuthorDate: Wed Aug 2 21:57:25 2023 +0530

    minor changes to comments within one of xalanj src file on this branch
---
 src/org/apache/xpath/compiler/XPathParser.java | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/src/org/apache/xpath/compiler/XPathParser.java b/src/org/apache/xpath/compiler/XPathParser.java
index 57eff6bf..9312a3e4 100644
--- a/src/org/apache/xpath/compiler/XPathParser.java
+++ b/src/org/apache/xpath/compiler/XPathParser.java
@@ -940,19 +940,20 @@ public class XPathParser
   /**
    * Expr   ::=   ExprSingle ("," ExprSingle)*
    * 
-   * We follow within this method, the XPath parsing with two pass approach,
-   *   1) The first pass, determines whether XPath 3.1's sequence 
-   *      constructor parsing needs to be used (with sequence items delimited 
-   *      by ',' operator), or to use the XPath parser's usual process using
-   *      '(' OpCodes.OP_GROUP ')'.
-   *   2) The second pass, is XPath parsing as usual, using the result
-   *      determined during step 1) above.
-   * 
    * @throws javax.xml.transform.TransformerException
    */
   protected void Expr() throws javax.xml.transform.TransformerException
   {
       if (fIsBeginParse && tokenIs("(")) {
+          // We implement within this 'if' branch, the XPath parsing with following 
+          // mentioned two pass approach,
+          // 1) The first pass, determines whether XPath 3.1's sequence (using comma
+          //    operator, to separate each of the sequence operands mentioned with 
+          //    this syntax) constructor parsing needs to be used, or to use this 
+          //    XPath parser's usual process using '(' OpCodes.OP_GROUP ')' to
+          //    parse an XPath expression delimited by braces '(' and ')'.
+          // 2) The second pass, is XPath parsing as usual, using the result
+          //    determined during step 1) as mentioned above.
           nextToken();                  
           
           List<String> sequenceConstructorXPathParts = new ArrayList<String>();


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xalan.apache.org
For additional commands, e-mail: commits-help@xalan.apache.org