Building with --enable-dummy results in warnings like this:
In file m_wkml_color.F90:159
subroutine kmlSetCustomColor(myCI, colorhex)
1
Warning (158): INTENT(OUT) variable 'myci' at (1) is never set
In file m_wkml_color.F90:180
function kmlGetColor_index(i) result(c)
1
Warning (139): Value of function 'kmlgetcolor_index' at (1) is never set
In file m_wkml_color.F90:195
function kmlGetColor_byName(name) result(c)
1
Warning (139): Value of function 'kmlgetcolor_byname' at (1) is never set
and like this:
In file fox_m_fsys_parse_input.F90:43
subroutine scalartostring(s, data, separator, csv, num, iostat)
1
Warning (158): INTENT(OUT) variable 'iostat' at (1) is never set
In file fox_m_fsys_parse_input.F90:194
subroutine scalartological(s, data, num, iostat)
1
Warning (158): INTENT(OUT) variable 'num' at (1) is never set
In file fox_m_fsys_parse_input.F90:194
subroutine scalartological(s, data, num, iostat)
1
Warning (158): INTENT(OUT) variable 'iostat' at (1) is never set
Should we fix these? I'm minded not to as this way we can use e.g. valigrand to find errors where the user application is dependent on FoX being compiled without --enable-dummy.
Building with --enable-dummy results in warnings like this:
and like this:
Should we fix these? I'm minded not to as this way we can use e.g. valigrand to find errors where the user application is dependent on FoX being compiled without --enable-dummy.