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

Coding Rules #276

Open
MarcBehrens opened this issue Jun 19, 2015 · 2 comments
Open

Coding Rules #276

MarcBehrens opened this issue Jun 19, 2015 · 2 comments
Assignees
@jensgerlach
Labels
Ready

Comments

@MarcBehrens
Copy link
Collaborator

related to openETCS/product-backlog#29

The coding rules for hand written code need to be detailed.
@MarcBehrens MarcBehrens reopened this Jul 3, 2015
@MarcBehrens
Copy link
Collaborator Author

relates to openETCS/modeling#522 basically there are two different ways to proceed. Either a generic way to handle real typed variables and their conversion or to try to avoid real typed variables.

It should be taken into account that according to Mü8004 from 01.08.2003 Teil 42 720 (6) the german national authority only allows
"char, unsigned char, short, unsigned short,
int, unsigned int, long, unsigned long, enum, void" as part of structured datatypes.

Type conversion between SCADE types and API types is one topic for the verification.
Mapping the SCADE API to the API definition has type conversions which need to be verified.

@MarcBehrens
Copy link
Collaborator Author

Concerning significance length see openETCS/modeling#303

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jensgerlach jensgerlach

Labels
Ready
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MarcBehrens @jensgerlach