The JADE C Application Programming Interface (API) has been extended, as follows. (For details, see
The JADE API jomcalls.h file now provides the following Application Programming Interface (API) call.
jomGetNodeContextHandle
The existing header file joscalls.h in the include directory on the JADE release medium now contains the following new functions.
josDskDateToGregorian
josDskTimeStampToGregorianHMSm
josDskTimeStampCompare
jomDecimalFromReal
jomDecimalFromInt64Scale
jomDecimalFromString
jomDecimalToReal
jomDecimalToString
jomDecimalCompare
The include directory on the JADE release medium now contains the new header file jombuild.h, which provides defines that enable you to perform build and runtime version checking. Each JADE Dynamic Link Library (DLL) exports a function named using the define MAKEMODULEVERSIONFUNC; for example, the function name exported by jomutil.dll in the 7.1.03 version of JADE is "moduleVersion_jomutil_7_1_03".
Static importers of the DLL can use the following to ensure that the importing DLL or executable, the jomutil.lib, and the jomutil.dll are consistent.
Declaration:
extern "C" DllImport int JOMAPI MAKEMODULEVERSIONFUNC(jomutil)();
Invocation:
int jomutilpatch = MAKEMODULEVERSIONFUNC(jomutil)();
If the jombuild.h version included by the user sources does not match the jomutil.lib, the compile‑time linker raises an error; for example:
mysource.obj : error LNK2019: unresolved external symbol __imp_moduleVersion_jomutil_7_0_7 referenced in function MyVersionChecker
At run time, if the importer version and the jomutil.lib version do not match jomutil.dll, the dynamic linker raises the following.
The procedure entry point moduleversion_jomutil_7_0_8 could not be located in the dynamic library jomutil.dll.