-
Notifications
You must be signed in to change notification settings - Fork 61
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
Interface file definitions naming #128
Comments
We have to consider interface names for R3TR objects and most probably LIMU objects. Furthermore, we have to define the naming for reuse interfaces (like the one for classes and interfaces; see #143). |
Yes, we can close this one |
agree, its dococumented and renaming is #151 |
Specification for the interface names of R3TR objects is available. Unfortunately, it is still unclear how interface names for LIMU objects shall be handled. See comments in #153. |
we currently have:
INTF
andCHKC
are the TADIR R3TR names, which are guaranteed to be unique, I suggest leaving out the "_oo" and "_atc" partsThe text was updated successfully, but these errors were encountered: