Skip to content

Wrong rule names left over in ECL parsing code #73

@mkorvas

Description

@mkorvas

I have identified a couple of changes in the ECL grammar between version 1.5 and 2.2 which were not apparently picked up by the ECL parsers in Hermes:

  1. In the typeIdFilter rule, Hermes looks for eclConceptReference on the RHS but ECL 2.2 has subExpressionConstraint there instead.
  2. In the acceptabilitySet rule, Hermes looks for acceptabilityIdSet on the RHS but ECL 2.2 has acceptabilityConceptReferenceSet there instead.
  3. In the dialectIdFilter rule, Hermes looks for eclConceptReference on the RHS but ECL 2.2 has subExpressionConstraint there instead.
  4. (This appears to be a copy-paste error rather than an omission in the ECL version upgrade.) In the dialectIdFilter rule, Hermes looks for dialectAliasSet on the RHS but ECL 2.2 has dialectIdSet there instead.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions