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

(pseudo) dynamic data types #3

Open
Kynneb opened this issue Aug 14, 2017 · 1 comment
Open

(pseudo) dynamic data types #3

Kynneb opened this issue Aug 14, 2017 · 1 comment

Comments

@Kynneb
Copy link
Collaborator

Kynneb commented Aug 14, 2017

When developing components which are to be included later in the workflow during the system integration step, one needs to provide fully specified ASN data types for the TASTE system to work.

However for more generic (i.d. reusable) components like a sensor driver library there are certain specifications which are not known at component development time but only when integrating the system, including specific hardware and software components.

Therefore the need for a possibility arises to be able to provide more generic data types which can be used during component development and fully specified during system integration.

@maltewi
Copy link
Member

maltewi commented Dec 20, 2017

The current workaround is documented here: https://github.com/ESROCOS/esrocos.github.io/wiki/pseudo_dynamic_data_types. Also the drawbacks of this approach.

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

3 participants
@Kynneb @maltewi and others