{"push_id":571636654,"size":1,"distinct_size":1,"ref":"refs/heads/develop","head":"41b2bb074b3cf6996d7e8bd3eee291d6ef5c1a90","before":"47ea7756c4830a436b302fc9ee813329f8b9cd2c","commits":[{"sha":"41b2bb074b3cf6996d7e8bd3eee291d6ef5c1a90","author":{"email":"16a9a54ddf4259952e3c118c763138e83693d7fd@optimojoe.com","name":"Joseph Young"},"message":"Fixed a bug where MATLAB would for iter_max to 0\n\nI fixed a bug where MATLAB/Octave would force iter_max to 0.  The\ndefault value for iter_max is std::numeric_limits <Natural>::max() from\nC++.  Basically, the largest unsigned integer that's architecture\ndependent (size_t).  Now, MATLAB/Octave can handle integers, sort of,\nbut it really just works with doubles most of the time.  As such, we end\nup casting these doubles to integers.  This generally works well, but\nthere was an issue when reading in a MATLAB/Octave state or reading in a\nMATLAB/Octave restart package that this would overflow.  Then, iter_max\nwould be set to 0, which caused all sorts of problems.  The fix is to\ncast ::max() and ::min() to doubles, compare to what C++ pulls from\nMATLAB/Octave, and then hard set to ::min() or ::max() if we detect an\nunder or overflow respectively.\n\nThis fixes #36.","distinct":true,"url":"https://api.github.com/repos/OptimoJoe/Optizelle/commits/41b2bb074b3cf6996d7e8bd3eee291d6ef5c1a90"}]}