Summary of Issue:
Currently, capgen does not have the pointer attribute. This has not been a problem because capgen does not create pointers and does not need to pass any pointers to CCPP schemes.
However, in order to check if a variable passed with the active metadata is correct (in debug mode), this information might be needed. The circumstances could be:
- The host model variable is a pointer
- The variable has the active attribute (not hardcoded or defaulted to
.true.)
- The lower bound of the variable is not 1 (or
ccpp_constant_one).
With this combination, the active check code could fail. At the very least, I think a case like this should be added to the unit tests and if it breaks, adding a pointer attribute might be a solution. In this case, capgen would add the pointer attribute to the group dummy argument. It should still (I think) be an error for schemes to have pointer variables, anyone have thoughts on this?
Are there other cases where the pointer attribute would a required addition to the defined metadata fields?
Summary of Issue:
Currently, capgen does not have the
pointerattribute. This has not been a problem because capgen does not create pointers and does not need to pass any pointers to CCPP schemes.However, in order to check if a variable passed with the
activemetadata is correct (in debug mode), this information might be needed. The circumstances could be:.true.)ccpp_constant_one).With this combination, the
activecheck code could fail. At the very least, I think a case like this should be added to the unit tests and if it breaks, adding apointerattribute might be a solution. In this case, capgen would add thepointerattribute to the group dummy argument. It should still (I think) be an error for schemes to have pointer variables, anyone have thoughts on this?Are there other cases where the
pointerattribute would a required addition to the defined metadata fields?