Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

problem in definition adl_relative_path. #24

Open
ghost opened this issue Feb 6, 2016 · 0 comments
Open

problem in definition adl_relative_path. #24

ghost opened this issue Feb 6, 2016 · 0 comments

Comments

@ghost
Copy link

ghost commented Feb 6, 2016

I give following command, in my specialized test (excuse the camelcase)
grun Test archetypeSlot -gui

Then I give this as argument:
allow_archetype OBSERVATION[id2] occurrences matches {0..1} matches { -- Vital signs
include
domain_concept/test matches {/blood_pressure.v2/}
domain_concept matches {/.*/}
}

It gives an error:
line 4:43 no viable alternative at input 'domain_conceptmatches'

If I change the input like this:
allow_archetype OBSERVATION[id2] occurrences matches {0..1} matches { -- Vital signs
include
domain_concept/test matches {/blood_pressure.v2/}
domain_concept/test matches {/.*/}
}

I get no error.

It is because of the definition of adl_relative_path which requires a slash somewhere in the string, else it cannot make a valid argument of it. This means that a relative path, consisting of one segment can never be valid.

This will not be a big problem in real life, it will not often happen that a relativepath without slash is used, but it is a weakness of the grammar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants