somtoolkit

I can believe that. It is not intended to be called multiple times within an application. In reality there should not really be a need to call it when a process ends because everything allocated by the som kernel should be local to the process.

Yes, in order to maintain binary compatibility with IBM's SOM the va exported functions need to be using the IBM optlink calling convention. This does not exist in the MSVC compiler so assembly stubs are used to maintain the compatibility If you look in https://sourceforge.net/p/somfree/code/HEAD/tree/trunk/som/src/somobjva.c you can see the extra assembly stubs used in Win32 with MSVC A version with the true MSVC linkages are included in the somtk.lib, see https://sourceforge.net/p/somfree/code...

During the IDL compilation the source file and line number are passed from the preprocessor to somipc. The idl file and line numbers are captured in the IR using the file and line modifiers. For win32 64 bit struct returns the IH uses the C compiler to determine the type size, eg look for the SOMRdRetsmallaggregate usages.

During the IDL compilation the source file and line number are passed from the preprocessor to somipc. The idl file and line numbers are captured in the IR using the file and line modifiers. For win32 64 bit struct returns the IH uses the compiler to determine the type size, eg look for the SOMRdRetsmallaggregate usages.

During the IDL compilation the source file and line number are passed from the preprocessor and to somipc. The idl file and line numbers are captured in the IR using the file and line modifiers. For win32 64 bit struct returns the IH uses the compiler to determine the type size, eg look for the SOMRdRetsmallaggregate usages.

That is excellent, well done! The use of somDumpSelf was very well done

That is excellent, well done!

That is excellent news! You are welcome to write one and add it to the discussions here.