Open peverwhee opened 4 months ago
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.
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
@DomHeinzeller OK, sounds like it'll be easiest to keep it in that order for the framework then. That's fine by me!
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.