[Octave-bug-tracker] [bug #38423] [k:l:m] not compatible for m = -0

[Rik]

Update of bug #38423 (project octave):

                  Status:                    None => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #6:

The situation isn't as bad as it appears.

For item #1, the print routine operates at human time scales.  The current
code will generate results much faster than they can be consumed either by a
pager (of order seconds until a user hits the space bar) or by a monitor (60
Hz).  

Special-casing the first element isn't attractive here because the body of the
loop is so large.

For item #2, min/max routines use deduction to eliminate needless
calculations.  Line 198 is correct because it is followed by lines 201/202.

+%!assert (r(1), -0)
+%!assert (min (r), -0)

The lines above are not duplicates.  "r(1)" tests that the elem() function
call works.  "min (r)" verifies that the function min() works.  The second
body of code in the min() routine is exercised by 

%!assert (min (rrev), -0)

which is several lines down in range.tst.

The operator '<<' is apparently unused which is why I didn't bother completing
this.  I need to ask jwe if this is truly unused and why we bother to keep it
around if it is.

    _______________________________________________________

Reply to this item at:

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

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