You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to the documentation mentioning what macros need to be set in the interface file for an app, there should be a compile time warning alerting the user to undefined values.
It might also be prudent to add validity checks against the entered values (for example when a bad MID was provided or a name exceeds a max value for the cfe).
The text was updated successfully, but these errors were encountered:
Doesn't the compiler already check if a macro is referenced without being defined? Is there some additional information that implementing this check in code could provide that the compiler doesn't?
It might be nice for a user to get a message indicating what/where the value should be but yeah the compiler warning should be enough to tell the user that a value isn't present.
In addition to the documentation mentioning what macros need to be set in the interface file for an app, there should be a compile time warning alerting the user to undefined values.
It might also be prudent to add validity checks against the entered values (for example when a bad MID was provided or a name exceeds a max value for the cfe).
The text was updated successfully, but these errors were encountered: