From octave-maintainers-request at bevo dot che dot wisc dot edu  Wed May 21 17:22:28 1997
Subject: Re: octave version
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: Doug Warner <warnerd at trinidad dot cs dot dartmouth dot edu>
Cc: Andreas dot Weingessel at ci dot tuwien dot ac dot at, octave-maintainers@bevo.che.wisc.edu
Date: Wed, 21 May 1997 17:21:48 -0500

On 21-May-1997, Doug Warner <warnerd at trinidad dot cs dot dartmouth dot edu> wrote:

| Correctly handling multiple versions of .oct files takes more work.
| You'd probably need to include version information with every shared
| library used by octave and make sure that the run-time system
| indicates an error if the .oct file was created with a different
| version of the shared libraries in mind.  I think that's not too hard
| on DEC Unix, but I don't know about other systems.

Instead of relying on some system-dependent method, would it be good
enough to use the OCTAVE_VERSION macro?  The .oct file could have this
compiled in, and then Octave could check it when installing the
function.  If the value in the .oct file failed to match the value in
the Octave binary, an (optional) warning could be printed.

jwe