Re: ga octave package maintenance

[edmund ronald]

Can't we do it like the C guys do, and have a compatibility flag? 

Or even better a line at the head of each file that says which version the author is using, and so subsequent releases know which flags they need to assume when loading that file?

Edmund

ᐧ

On Tue, Jul 24, 2018 at 8:36 PM, JohnD <address@hidden> wrote:

From: edmund ronald [mailto:address@hidden]
Sent: Tuesday, July 24, 2018 1:41 PM
To: JohnD
Cc: octave-maintainers
Subject: Re: ga octave package maintenance

Much of numerical or semi-numerical code out there is historical.
It might make more sense to figure out why new releases of Octave break things than to hope to force maintainers to track code changes.

Edmund
ᐧ

------

Well in the case of ga, it was code that was returning a value that was never being set. Older versions of octave didn’t care. Newer versions do.