Re: should Octave be more strict about checking number of arguments?
Markus Mützel <[email protected]>
| Newsgroups | gmane.comp.gnu.octave.maintainers |
|---|---|
| Message-ID | <trinity-56d59541-3677-4998-96e1-49dff98fc0bd-1594624246079@3c-app-gmx-bap44> |
Am 12. Juli 2020 um 23:57 Uhr schrieb "John W. Eaton": > I pushed the following changesets to default: > > http://hg.savannah.gnu.org/hgweb/octave/rev/b0b80efecea1 > http://hg.savannah.gnu.org/hgweb/octave/rev/5a07c798eb08 > http://hg.savannah.gnu.org/hgweb/octave/rev/1dd765e54265 > > The first makes is an error to call a function with more inputs or > outputs than the function can accept or produce. The second fixes > Octave functions and tests to avoid these errors. The third change > fixes tests that expect an error to match the new "function called with > too many inputs/outputs" error message instead of the older "invalid > function call" error. > > This change is probably too disruptive for stable, but applying it now > on default should give us time for testing before version 7 is released. > If it causes too much trouble, we can generate a warning instead of an > error by default. > > jwe > > I agree that the default branch is the one for this kind of changes. It's possible they cause existing code to fail. We should probably let people know about this change with a note in the NEWS file. Markus