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

Scheme for avoiding conflict of error numbers #8

Open
CesarCoelho opened this issue Jun 29, 2016 · 1 comment
Open

Scheme for avoiding conflict of error numbers #8

CesarCoelho opened this issue Jun 29, 2016 · 1 comment
Labels
Proposed R3 Proposed for R3 of Blue Book

Comments

@CesarCoelho
Copy link

I have noticed that the MAL complains when I try to deepInit a certain Area when one has repeated error numbers.
For example, I have 2 different sets of services Platform and Software Management services. However, because I was numbering them sequentially starting it with 1, there was an overlap of errors during the initialization and the MAL implementation complained during runtime.
I have checked the COM services and this is what you have defined:

INVALID 70000
DUPLICATE 70001

Sam's answer:
No, there is no scheme for avoiding conflict of error numbers. Its probably worth raising a RID on the MAL spec for this.

@CesarCoelho
Copy link
Author

After discussing it with Sam, it was agreed to follow the following convention on the short-term:
0xAAVSEEEE

At the moment this will only truncate zeros however we could find a migration solution in the future to allow versions higher than 15 and errors for areas with more than 15 services.

@SamCooper SamCooper added the Proposed R3 Proposed for R3 of Blue Book label Apr 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Proposed R3 Proposed for R3 of Blue Book
Projects
None yet
Development

No branches or pull requests

2 participants