Re: ranges?

[Dmitri A. Sergatskov]

On 8/22/06, John W. Eaton <address@hidden> wrote:

> Class must be double for compatibilty.  Internally, Octave still has a
> special data type to represent ranges.  That's why you see only 24
> bytes used in the first case.  Most (all?) arithmetic operations on
> ranges result in matrices though, so that's why you see 80 bytes used
> in the second case.  Adding optimized operations for ranges is
> possible, but someone has to do the work.

I understand the conversion. I just was confused by apparent contradiction
between the Size and the Class for idx. Now I understand the reason.

> See also the typeinfo function, which returns the name of the internal
> data type instead of the Matlab-compatible class name.

Thanks.

> jwe

Dmitri.
--