You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@xalan.apache.org by bu...@apache.org on 2003/04/04 20:15:40 UTC

DO NOT REPLY [Bug 18720] New: - Current Node and Context Node terminology

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18720>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18720

Current Node and Context Node terminology

           Summary: Current Node and Context Node terminology
           Product: XalanJ2
           Version: 2.5Dx
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: org.apache.xalan
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: igorh@ca.ibm.com


This is actually a suggestion.
In code and comments (a lot of files) we use incorrect terminology.
We use Current Node when we mean Context Node and vice versa. 
As an example (see below from  XPathContext).
1. "current context node" is wrong terminology
2.  getContextNode returns getCurrentNode()
 (getCurrentNode() is final).
/**
   * Get the current context node.
   * @return The current context node.
   */
  public final int getContextNode()
  {
    return this.getCurrentNode();
  }