We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The framework sometimes uses "errcode, errmsg" in the calling list and sometimes has "errmsg, errcode". It would be nice if this was consistent.
The NCAR SEs are leaning towards "errcode, errmsg", but are happy either way.
Modify all calling lists (in generated code and in static src code) to adhere to ordering we decide.
The text was updated successfully, but these errors were encountered:
In the UFS, it's consistently errmsg, errflg
errmsg, errflg
Example: https://github.com/ufs-community/ccpp-physics/blob/ufs/dev/physics/CONV/Grell_Freitas/cu_gf_driver.F90
Sorry, something went wrong.
@DomHeinzeller OK, sounds like it'll be easiest to keep it in that order for the framework then. That's fine by me!
No branches or pull requests
Description
The framework sometimes uses "errcode, errmsg" in the calling list and sometimes has "errmsg, errcode". It would be nice if this was consistent.
The NCAR SEs are leaning towards "errcode, errmsg", but are happy either way.
Solution
Modify all calling lists (in generated code and in static src code) to adhere to ordering we decide.
The text was updated successfully, but these errors were encountered: