| Re: Another small V8.0 bug [message #71883 is a reply to message #71881] |
Mon, 26 July 2010 11:44   |
wlandsman
Messages: 743
Registered: June 2000
|
Senior Member |
|
|
On Jul 26, 2:24 pm, Paulo Penteado <pp.pente...@gmail.com> wrote:
> Yes, that sort of problem was always possible whenever a new intrinsic
> function is introduced. Or when one installs some new third-party
> library, or just some function from someone who does not try to make
> the routine names more likely to be unique. But it is not a new issue,
> it has always been a consequence of the () ambiguity.
Yes, but not only is "list" a common variable name, but since the list
function can accept any data type, one won't get any error in the
initial function call. I am used to seeing errors like the
following
IDL> obj_new = indgen(10)
IDL> print,obj_new(3)
% OBJ_NEW: String expression required in this context: <INT
( 3)>.
% Execution halted at: $MAIN$
which tells me right away that I am calling a function named OBJ_NEW()
rather than subscripting an array. But I don't believe that a =
list( foo) will ever give an error, and it is only when trying to use
the variable that one will encounter the (less obvious) error.
Thanks again. --Wayne
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
