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

Allow additional entry points in FMU code, specify restrictions #1643

Closed
pmai opened this issue Jan 25, 2022 · 1 comment · Fixed by #1649
Closed

Allow additional entry points in FMU code, specify restrictions #1643

pmai opened this issue Jan 25, 2022 · 1 comment · Fixed by #1649
Assignees
Milestone

Comments

@pmai
Copy link
Collaborator

pmai commented Jan 25, 2022

As per the discussion on #1632, in order to properly support both minor releases with new optional features, as well as layered standards, we should clarify in the standard that additional entry points in FMUs (binary/source code) are allowed (they already have to be to follow OS ABI requirements), and that we reserve all symbols starting with fmi3 for FMI 3.x.

@pmai
Copy link
Collaborator Author

pmai commented Jan 25, 2022

Note that we currently require symbols for optional features to be present, even if the feature is not supported. For additional features in minor releases we cannot continue requiring this; so this might be considered a variance...

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

Successfully merging a pull request may close this issue.

1 participant