Overloaded inbuilt operators causing maximum recursion errors

1 view (last 30 days)
I am trying to do overloaded inbuilt operators, such as overloading == (eq) for A == B (or eq(A,B)).
I did this: In my working directory I created a new folder 'overloads' , within that directory created a folder @double, and then the function eq.m which is my overloaded function:
function [result] = eq(A,B)
if abs(A-B)<1e-12
result = 1;
else
result = 0;
end
This seems to work fine. The problem is I am getting weird behavior after creating this overloaded function. For example whenever I subtract two numbers in the command line, such as 4-5, or 2 - 3 (any numbers really), I get this error: "maximum recursion limit of 500 reached... etc'. Whenever I try to use any operators, even ones I have not overloaded, I get this weird behavior .
Any ideas?
  6 Comments
JMP Phillips
JMP Phillips on 21 Dec 2015
Walter, if you mean that MATLAB's comparison routine involves some sort of recursion then that may explain it but I don't understand it.
Changing to logicals did not resolve the issue (was working yesterday, not today), so must be something else.
Additionally, when I try to open the function file from within matlab, it also gives a recursion error.
Anyway thanks for your answers much appreciated.

Sign in to comment.

Accepted Answer

Walter Roberson
Walter Roberson on 17 Dec 2015
function [result] = eq(A,B)
result = abs(A-B)<1e-12);
end
Notice this returns logical not double. In your code the double 0 and double 1 you returned would have had to have been compared against 0 by MATLAB in order to try to figure out whether the value you had returned was true or false.
I recommend, by the way, that you specifically comment how your code will deal with NaN and with vectors or arrays and with comparing values of different size()
I also recommend that you consider making the tolerance a relative tolerance based upon eps.
  5 Comments
Walter Roberson
Walter Roberson on 17 Dec 2015
Edited: Walter Roberson on 18 Dec 2015
When you overload an existing class operator you are not making any explicit references, you are messing with ALL use of the operator (except for nested functions in the original implementation, those take local precedence.) Overloading is nearly unscoped.
But the poster did not ask us if this was a good idea, or ask us how to confine the effects to particular routines. The poster has already gone as far as to keep the power supply on while opening the cover of the No User Serviceable Parts section, and I am okay with them finding out experimentally what can go wrong.

Sign in to comment.

More Answers (0)

Categories

Find more on Loops and Conditional Statements in Help Center and File Exchange

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!