[Octave-bug-tracker] [bug #32980] for backend FLTK, real is used for axes. double should be used

[Michael Godfrey]

Follow-up Comment #10, bug #32980 (project octave):

Thanks Rik.

Since choice 1 would be at best unreliable I agree that
choice 2 is better, and easier.  It may be appropriate
to issue the warning at a value less than realmax("single")
and change the message to read something like "axis
and data values near realmax("single") or realmin("single")
may produce incorrect plots due to overflow/underflow"

And, your elimination of for loops is appropriate, of
course.  I try to do that too, but this code was a quick
test and copied from similar loops in axis.m...
Rounding to zero may be right, too.

Michael

    _______________________________________________________

Reply to this item at:

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

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