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

Define AST without inheriting Namespace #106

Merged
merged 1 commit into from
Feb 6, 2024
Merged

Conversation

gunnarx
Copy link
Collaborator

@gunnarx gunnarx commented Jan 30, 2024

At an early stage, the top level was defined by a toplevel namespace.
However the specification/examples treats the top level slightly differently.
In the meantime, some of the code was tested by treating Namespace to top level node instead of the AST type and (in quite a sloppy way) just achieving that by inheriting Namespace.

This commit is an old fix that should have been pushed a long time ago. It brings things into order by clearly defining the file top-level (represented by the AST class) as an independent thing.

From here, we are back in sync with the current formal specification, and we can from there proceed to make slight modifications - such as clarifying where the versioning should occur (it should be applied to an Interface, not on "file" level) and other quality improvements.

@gunnar-mb gunnar-mb merged commit 3c957d4 into COVESA:master Feb 6, 2024
3 checks passed
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 this pull request may close these issues.

2 participants