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

Clarify which AUTOSAR type categories are appropriate to represent array types #32

Open
TorstenGoerg opened this issue Jul 11, 2019 · 2 comments

Comments

@TorstenGoerg
Copy link
Collaborator

May be, fixed-sized arrays should be converted to the category "ARRAY" and dynamic arrays to "VECTOR".

@gunnarx
Copy link
Contributor

gunnarx commented Jul 11, 2019

Those are good names to use, in my opinion. I suppose the comparison/translation table should clarify which type translates to which?

@TorstenGoerg
Copy link
Collaborator Author

TorstenGoerg commented Jul 11, 2019

Those are good names to use, in my opinion. I suppose the comparison/translation table should clarify which type translates to which?

It is not just a question of naming. Data type categories like ARRAY and VECTOR are specified by the AUTOSAR standard with a particular meaning (see "AUTOSAR_TPS_ManifestSpecification.pdf").
The mapping table (https://docs.google.com/spreadsheets/d/1O7gMTK1oaDHi43G2B6-Es5H4okzcjvmeRyW7sUPnAaQ/edit#gid=0) currently does not distinguish fixed-sized and dynamic arrays because this difference is visible in the deployment data only on Franca side. The detailed mapping analysis of deployment data is open yet. Currently, the mapping table suggests to map arrays always to the AUTOSAR category VECTOR because this is the more general case.

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

2 participants