Removing a duplicate use statement of FMS function "write_version_number"#98
Merged
Merged
Conversation
…use fms_mod, only: write_version_number now.
6 tasks
bensonr
approved these changes
Apr 30, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The FMS 2021.02-beta1 testing tag code requires the
write_version_numbersubroutine be loaded from fms_mod. Any use ofwrite_version_numberfrom fms_io_mod will now give a compilation error. tools/fv_diagnostics.F90 has loaded this subroutine via both fms_io_mod and fms_mod. This PR removes the fms_io_modwrite_version_numberuse statementFixes # (issue)
How Has This Been Tested?
I have verified this works when testing for PR #74. I have also verified that the code compiles with FMS tag 2021.02-beta1.
Checklist:
Please check all whether they apply or not