ModNewest - Load in the Newest Module

My first piece of software to be released this year and my first written in C++ that I am releasing. Thanks to Paolo Fabio Zaino for the starting point with the C code for GCC to make a module, a good starting point to get C++ working.

ModNewest will load the newest module your system has seen by overriding the *RmLoad command which many applications use. It has a look in !System and a few other places to see if can find something newer.

Then a copy of the newest module once found is made (into your Choices.ModNewest directory) and this will be used in future for comparisons so that you will be loading the newest that your system has ever seen.

If a *RmLoad tries to load in an older version of a module that is already running, the request is simply ignored.

(Some modules are excluded for technical reasons including Amulator – the normal RmLoad operation will work instead)

There is a more complete description on the website and !ReadMe file available at: http://www.ro32.co.uk

It is completely free for anyone to use, distribute. No source code at the moment.

Does it cope with several different versions of a module all with the same version number?

Does it cope with several different versions of a module all with the same version number?

Yes, if the modules have the date in the help string this is checked. The one with the highest version number is loaded and if there are a several with the same version number, it is only then that the date is checked. When it finds several with the same version and date it will load them in a specific order – the file your *RmLoad command points to always takes priority if it is one of multiple found with the same version and date.

I have noticed the date is not checked against running versions of the module, so I will get that added.

If you wish to try and want to know which modules were loaded, the information can be found in system variables that are named ModNewest$@…ModuleName… – That contains the file location of what was loaded, the version number and date.

My original post does not mention that you can still use the standard *RmLoad command by adding a percent sign: *%RmLoad.

I’ve just upload version 0.02 which now does check the date and version numbers for the currently loaded module against others found on disc.