Skip to content
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

Update CCPP tech doc: pointer variables are not allowed in CCPP-compliant parameterizations #541

Open
climbfuji opened this issue Mar 1, 2024 · 3 comments
Labels
ccpp_prebuild bugs, requests, etc. that involve ccpp_prebuild documentation enhancement

Comments

@climbfuji
Copy link
Collaborator

Description

We've determined that CCPP will not support pointer variables in CCPP-compliant parameterizations, so let's add this information to the CCPP technical documentation.

@mkavulich
Copy link
Collaborator

@climbfuji I'm in the process of updating the Technical Documentation now. Just to clarify, internal pointers within physics schemes will still be allowed, right? They will just not be supported as CCPP-compliant variables passed between schemes/hosts?

@climbfuji
Copy link
Collaborator Author

@climbfuji I'm in the process of updating the Technical Documentation now. Just to clarify, internal pointers within physics schemes will still be allowed, right? They will just not be supported as CCPP-compliant variables passed between schemes/hosts?

Yes, as far as I remember this is correct.

@mkavulich
Copy link
Collaborator

Another note here while I'm wrapping my head around things: I noticed all of the framework code for dealing with pointers is still present (for example, the "pointer" attribute added in #552) as well as unit tests. I assume these will be removed in the future?

I added wording here and here that I think properly captures the current state of things, let me know what you think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ccpp_prebuild bugs, requests, etc. that involve ccpp_prebuild documentation enhancement
Projects
None yet
Development

No branches or pull requests

2 participants