Changes to make range checking optional [0.5 d]

[Ian Culverwell]

https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_io/ropp/ropp_io.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_io/ropp/ropp_io_read.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_io/ropp/ropp_io_read_ncdf_get.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_io/tools/eum2bufr_ec.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_io/tools/eum2ropp.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_io/tools/ropp2bufr_ec.f90 (similar/consistent updates to ropp2bufr_mo.f90 has not been made since https://trac.romsaf.org/ropp/changeset/3430)

Original changesets:

Changes to make range checking optional: https://trac.romsaf.org/ropp/changeset/4272/ropp_src/branches/dev/Share/dmi_trunk_6.1/ropp_io/tools/eum2ropp.f90

[Ian Culverwell]

--no-ranchk is already an option in the base code. The only changes to include are ranchk=ranchk clauses in calls to ropp_io_thin and ropp_io_write. These are well established routines, so we don't need to do any more testing than to check that it compiles and runs OK. It does. Note that, in accordance with general policy, we do not advertise the --no-ranchk option, and, in view of the workaround discussed in #564, we don't switch off the warning that it's being invoked either.

Changes made at r6236. Closing ticket.