-
Notifications
You must be signed in to change notification settings - Fork 142
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
Bugzilla 1972: add_hist_coord - look into misleading overloading #2
Comments
jimmielin
pushed a commit
to jimmielin/CAM
that referenced
this issue
May 31, 2020
Fix an infinite loop issue
jtruesdal
added a commit
that referenced
this issue
Aug 6, 2020
Cam development merge latest cam6_2_037
gold2718
pushed a commit
to gold2718/CAM
that referenced
this issue
Jan 27, 2021
…_alpha02a Fix for missing no_fill argument
jimmielin
pushed a commit
to jimmielin/CAM
that referenced
this issue
Feb 24, 2021
[CESM-GC] Add MAM4 coupling
gold2718
pushed a commit
to gold2718/CAM
that referenced
this issue
Apr 24, 2023
Replaced MICOM with BLOM in bld/config_files/definition.xml.
gold2718
pushed a commit
to gold2718/CAM
that referenced
this issue
Apr 24, 2023
initialisation and redundant code merge
gold2718
pushed a commit
to gold2718/CAM
that referenced
this issue
Nov 29, 2023
Untabify config_compsets.xml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Opened: Cheryl Craig 2014-05-08 14:12:48 MDT
add_hist_coord has 3 overloaded specific routines.
The actual minimal user interface is (name, value, label). If a user neglects to specify 3 values and only gives two (name, value), one of the overloaded routines (add_hist_coord_regonly) is called and value is overwritten with index.
This is misleading and should probably look at whether add_hist_coord_regonly should be part of the add_hist_coord overloading or not.
Reviewed: Cheryl Craig 2016-05-04 14:12:07 MDT
This might go away with the refactor.
The text was updated successfully, but these errors were encountered: