Opened 15 years ago

Closed 14 years ago

#209 closed enhancement (fixed)

Inquirey function for ROPP version

Reported by: Dave Offiler Owned by: Michael Rennie
Priority: normal Milestone: 5.0
Component: ROPP (all) Version: 4.0
Keywords: inquiry, function, version Cc: huw.lewis@…

Description

Johannes Fritzer (GFZ) requests a function to ruturn the ROPP version number:

2) Additionally, when using ROPP routines, it is sometimes
desirable to query the ROPP version information, similar to the
NetCDF nf90_inq_libversion() or the HDF5
h5get_libversion() routines.
A  simple "subroutine message_get_roppVersion(roppMajorNumber,
roppMinorNumber, roppReleaseNumber, roppErrorCode)"
could do this (as indicated in the attached file ropp_utils_messages.f90 (line 128).
Is there a chance to include such a routine in the next release?

The attached file mentioned is attached to #208.

Change history (3)

comment:1 by Ian Culverwell, 14 years ago

This is a follow-on from #208.

After discussion with Johannes, he agreed to let us amend the call to

message_get_roppVersion(roppMajorNumber, roppMinorNumber, roppPatchNumber, roppErrorCode)

rather than the potentially ambiguous

message_get_roppVersion(roppMajorNumber, roppMinorNumber, roppReleaseNumber, roppErrorCode)

Thus, we are currently working at ROPP 5.0.0, where the last is the patch number.

Note that the whole business of referring to ROPP versions could be improved: take it automatically from (eg) configure.am files which know the version; allow different versions per module (not recommended); use this routine to supplant myriad version = ADJUSTL("5.0") statements in the fortran of the ropp tools. But this will suffice for now.

comment:2 by Ian Culverwell, 14 years ago

Note as before (#208) that this is just an interface routine.

comment:3 by Ian Culverwell, 14 years ago

Resolution: fixed
Status: newclosed

Close ticket after successfully passing changes through test folder.

Note: See TracTickets for help on using tickets.