Precedence : tests... and bugs ?

[Julien Bect]

Michael Goffioul wrote
> Precedence is established for classes, not objects.
> Even when constructing a second object of a given class, you change the
> precedence rules, this will affect all objects of the class, even those
> already constructed. And if you define a precedence between 2 classes,
> later on you can't redefine its inverse (afaik it'll generate an error).

I have started to write tests for the precedence mechanism, since
test/classes/test_classes.m contains very little about this.

While doing so, I have stumbled upon several weird behaviours that look very
much like bugs.

I will keep investigating this issue, more on this later.



--
View this message in context: 
http://octave.1599824.n4.nabble.com/Precedence-tests-and-bugs-tp4649510.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.