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.

Sign up for GitHub

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

Jump to bottom

Allow components to implement "interfaces," i.e., sets of ports #317

Open
bocchino opened this issue Aug 28, 2023 · 0 comments
Open

Allow components to implement "interfaces," i.e., sets of ports #317

bocchino opened this issue Aug 28, 2023 · 0 comments
Labels
proposed feature A proposed new feature semantics Issues related to semantics spec Issues related to the FPP language specification syntax Issues related to syntax user's guide Issues related to the FPP User's Guide

Comments

@bocchino
Copy link
Collaborator

bocchino commented Aug 28, 2023 •
edited
Loading

Here is an example, in which the interfaces are represented as included files:

nasa/fprime#2252

Each component that includes ByteStreamDriverInterface.fppi gets those ports and provides its own implementation for the input port handlers.

It would be nice to support these interfaces as a first-class FPP feature.
@bocchino bocchino added proposed feature A proposed new feature semantics Issues related to semantics spec Issues related to the FPP language specification syntax Issues related to syntax user's guide Issues related to the FPP User's Guide labels Nov 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
proposed feature A proposed new feature semantics Issues related to semantics spec Issues related to the FPP language specification syntax Issues related to syntax user's guide Issues related to the FPP User's Guide
Projects
FPP Proposed Features
Status: To Do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bocchino