Skip to content

Possible (minor) issue with attribute types  #366

Open
Open
Possible (minor) issue with attribute types #366

Description

@goto40
goto40
opened on Jan 30, 2022

Playing around with the meta model properties I added some tests: https://github.com/textX/textX/tree/feature/additional_metamodel_tests

I found a possible issue I would like to discuss:

In the docu we have "If there are multiple common rules than the first will be used as a result and the rest only for parsing".

Based on this sentence I tried:

        Model: 'value' x=Base;
        Base: S1|(S2 NotS3); // only use first rule (S2) as possible instance for each choice-option
        S1: name=ID;
        S2: name=ID;
        NotS3: name=ID;

In this meta model Base should not be a base of NotS3... I think this is a possible issue (probably not so difficult to fix).

Activity

  1. igordejanovic commented on Jan 31, 2022

    @igordejanovic
    igordejanovic
    on Jan 31, 2022
    Member

    I think you are right. It looks like a potential problem. The metamodel should be consistent with the parsing results. Since NotS3 instance is never instantiated during Base parsing (i.e. it will be thrown away after parsing) it shouldn't be its subclass.

  2. goto40 commented on Jan 31, 2022

    @goto40
    goto40
    on Jan 31, 2022
    MemberAuthor

    I will have a look...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions