macro for building packages with different Octave versions

[Olaf Till]

Hi,

symbols in Octave sometimes change, requiring some consideration if
packages with C++ code should be compatible with several major Octave
versions.

Some time ago Carnë offered some tests for single deprecated symbols
in Octave.

My strategy has been not to test, but to use the deprecated symbols as
long as possible and then to switch to the new symbols. But this
strategy doesn't seem to work, since not all deprecated symbols are
available for more than one major Octave version.

Trying to simplify checking for and building with simple cases of
alternative Octave symbols, I made an autoconf macro which does the
more tedious part of the job. It probably should be made available at
the Octave Forge website. My programming of autoconf macros is not
very good, so I'd appreciate comments and improvements. The macro and
an example call are at:

https://savannah.gnu.org/patch/index.php?9410

The macro file contains a further explanation in the comment block
above the second macro.

Olaf

-- 
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net

signature.asc
Description: Digital signature