[Octave-bug-tracker] [bug #32924] lcm does not warn when losing precision

[Jordi Gutiérrez Hermoso]

Follow-up Comment #17, bug #32924 (project octave):

Thanks for the nudge, Rik. I applied Cornelius's patch, but then I realised it
wasn't exactly right. Turns out it's a bit more work to do this correctly in
order to account for all possible Octave types (floats, integrals, complexes,
sparse). I spend some time during the past two days trying to get this to work
with templates, but I couldn't do it, and I think I will just macro it
instead. Sadface.

Please bear with me. I'll try to get the right patch in during the next couple
of days. I'm trying to make it general enough so that other integer functions
can warn when floats are used outside the integer range. After working on this
patch, I realised how important it was to make this work in general.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?32924>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/