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

Misleading definition of QualifiedName expression #70

Closed
AndreyG opened this issue Sep 17, 2022 · 1 comment · Fixed by #71
Closed

Misleading definition of QualifiedName expression #70

AndreyG opened this issue Sep 17, 2022 · 1 comment · Fixed by #71

Comments

@AndreyG
Copy link
Contributor

AndreyG commented Sep 17, 2022

Definition of QualifiedName says (sec:ifc:ExprSort:QualifiedName)

The elements field designates the sequence of unqualified names (ExprSort::UnqualifiedId)...

but actually part of qualified name could be not only UnqualifiedId, but also TemplateId.

@GabrielDosReis
Copy link
Collaborator

You're right ExprSort::QualifiedNamed should really be renamed to reflect the C++ standards' qualified-id

GabrielDosReis added a commit to GabrielDosReis/ifc-spec that referenced this issue Sep 22, 2022
The component are NOT restricted to `ExprSort::UnqualifiedId`.

Fix microsoft#70
GabrielDosReis added a commit that referenced this issue Sep 22, 2022
The component are NOT restricted to `ExprSort::UnqualifiedId`.

Fix #70
GabrielDosReis added a commit that referenced this issue Sep 22, 2022
The component are NOT restricted to `ExprSort::UnqualifiedId`.

Fix #70
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

Successfully merging a pull request may close this issue.

2 participants