[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: behavior of arrays
- Subject: Re: behavior of arrays
- From: Jack Saba <jack(at)icesat1.gsfc.nasa.gov>
- Date: Thu, 20 May 1999 09:05:26 -0400
- Newsgroups: comp.lang.idl-pvwave
- Organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA
- References: <37432ECC.5E76770A@fz-juelich.de>
- Xref: news.doit.wisc.edu comp.lang.idl-pvwave:14829
But more often than not, I WANT the extra dimension to be lost,
or at least I want IDL to be willing to ignore it where appropriate.
Consider this unrealistic example that nevertheless illustrates a
problem that occurs all too often in IDL:
IDL> ijk=where(x eq 10)
IDL> for i=ijk,99 do print, i
% Expression must be a scalar in this context: I.
% Execution halted at: $MAIN$
I could have written i=ijk,99, or i=REFORM(ijk),99 to avoid the
error. But it shouldn't be necessary -- this should be handled
> I have some problems to understand the logic which may be behind the
> handling of an array
> like defined.
> Why is the result help, b.d only  and not [10,1] ?
> This means I will lose the information that's it is / was a 2-dim
> ;D FLOAT = Array[10, 1]
> ;** Structure <1348428>, 1 tags, length=40, refs=1:
> ; D FLOAT Array[10, 1]
> ; <Expression> FLOAT = Array
> ; C FLOAT = Array