comp.lang.idl-pvwave archive: archive » Should SORT(Undefined) give an error message?

Home » Public Forums » archive » Should SORT(Undefined) give an error message?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Should SORT(Undefined) give an error message? [message #93038 is a reply to message #93037]

Wed, 13 April 2016 14:03

Lajos Foldy
Messages: 176
Registered: December 2011

Senior Member

On Wednesday, April 13, 2016 at 7:28:13 PM UTC+2, wlandsman wrote:
> Currently one can SORT() an undefined variable without getting an error message
>
> IDL> sort(undefined)
> 0
>
> Certainly, the current result is inconsistent with the documentation:
>
> "The result is always a vector of integer type with the same number of elements as Array." since in this case Array has 0 elements.
>
>
> I think one should get an error message the same way one does with sqrt(undefined) or max(undefined)
>
> In my case, the current behavior slowed down my debugging because I was using the sort index of Vector A to sort another vector B. Vector A was mistakenly undefined but Vector B was valid. Therefore, B[SORT(A)] was also valid, and the program happily proceeded. --Wayne

I think it's a bug. It gives an error message in GDL or FL.

regards,
Lajos

Report message to a moderator

[Message index]

		Should SORT(Undefined) give an error message? By: wlandsman on Wed, 13 April 2016 10:28
		Re: Should SORT(Undefined) give an error message? By: Lajos Foldy on Wed, 13 April 2016 14:03

Previous Topic:	Looping over odd values only
Next Topic:	3d Interpolation

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Nov 28 13:29:55 PST 2025

Total time taken to generate the page: 0.00792 seconds