[Octave-bug-tracker] [bug #45758] for 'range' type input some functions fail to return type range

[John W. Eaton]

Follow-up Comment #5, bug #45758 (project octave):

I created the range type as a space optimization for the colon operator in the
scripting language because I didn't think it made sense to run out of memory
for an expression like


for i = 1:huge_number
  ...
end


I could have restricted this optimization just to FOR loops, but then things
like the above would be allowed but


x = 1:huge_number;
for i = x
  ...
end


would still fail.  It didn't occur to me to also allow the range type to allow
integer types or to be N-dimensional (with all but one dimension == 1).  I
suppose we could make those changes now if we really wanted to, but it seems
like a lot of work for little gain.

    _______________________________________________________

Reply to this item at:

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

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