| Re: Reading Others Code [message #60558 is a reply to message #60529] |
Thu, 22 May 2008 12:55   |
Michael Galloy
Messages: 1114
Registered: April 2006
|
Senior Member |
|
|
On May 22, 1:25 pm, David Fanning <n...@dfanning.com> wrote:
> A friend of mine and I have been reading each others
> IDL code lately. It's truly amazing what you can learn
> by doing this!
>
> Anyway, I have this line of code in one of my programs:
>
> HELP, CALLS=callstack
>
> He was flabbergasted. Apparently, this keyword is not
> documented. I'm dumbfounded, too, since I don't usually
> use undocumented code.
>
> Here is my question. Was this ever documented? Does
> anyone else know about this?
I don't know the answer to your question, but it does bring up two
separate issues for me:
1. SCOPE_TRACEBACK is the "approved" way to do this now, but returns
the call stack in reverse order.
2. I recently needed to know the routines that have been added to
IDL since 6.1 (updating the known routines for the TextMate IDL
plugin). It would be nice to not have to install four versions of IDL
to answer these questions. The online help is HTML-based. Why can't I
just look these things up on the ITT VIS website?
> P.S. You can tell this is an old IDL keyword, because
> CALLS obviously stands for "CALLSTACK", and yet you
> can't use "CALLSTACK". This is one of my favorite pet
> peeves about IDL, but I think the programmer who used
> to do this all the time has now moved on.
Yes, I hate this too (my "favorite" is the SUBEXPR keyword to
STREGEX).
Mike
--
www.michaelgalloy.com
Tech-X Corporation
Software Developer II
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
