Re: IDLWAVE 4.5 [message #22042] |
Tue, 17 October 2000 00:00 |
Kenneth Mankoff
Messages: 42 Registered: August 1999
|
Member |
|
|
On 16 Oct 2000, Carsten Dominik wrote:
> IDLWAVE 4.5 fixes a few minor bugs in the object support.
> (reported by JD Smith, as usually - is anybody else using this?).
> http://www.strw.leidenuniv.nl/~dominik/Tools/idlwave
> - Carsten
Hi Carsten,
i use it, and love it. I even got our sysadmin to do a site install of
it... not sure anyone else in the building (LASP) uses it, but i do.
Thanks,
ken.
|
|
|
Re: IDLWAVE 4.5 [message #22052 is a reply to message #22042] |
Mon, 16 October 2000 00:00  |
Paul van Delst
Messages: 364 Registered: March 1997
|
Senior Member |
|
|
"J.D. Smith" wrote:
>
> Carsten Dominik wrote:
>>
>> IDLWAVE 4.5 fixes a few minor bugs in the object support.
>> (reported by JD Smith, as usually - is anybody else using this?).
>>
>> http://www.strw.leidenuniv.nl/~dominik/Tools/idlwave
>
> Maybe it's just that only I use it so fervently. Perhaps we should
> start a tasty tidbit of the week column so those who are missing out can
> either continue salivating or finally give Idlwave a try.
>
> Here's one:
>
> You're running a deeply convoluted program in IDL.
Well, there's your problem right there! The deep convolution, I mean.
Not IDL.
:o)
paulv
--
Paul van Delst Ph: (301) 763-8000 x7274
CIMSS @ NOAA/NCEP Fax: (301) 763-8545
Rm.202, 5200 Auth Rd. Email: pvandelst@ncep.noaa.gov
Camp Springs MD 20746
|
|
|
Re: IDLWAVE 4.5 [message #22054 is a reply to message #22052] |
Mon, 16 October 2000 00:00  |
John-David T. Smith
Messages: 384 Registered: January 2000
|
Senior Member |
|
|
Carsten Dominik wrote:
>
> IDLWAVE 4.5 fixes a few minor bugs in the object support.
> (reported by JD Smith, as usually - is anybody else using this?).
>
> http://www.strw.leidenuniv.nl/~dominik/Tools/idlwave
Maybe it's just that only I use it so fervently. Perhaps we should
start a tasty tidbit of the week column so those who are missing out can
either continue salivating or finally give Idlwave a try.
Here's one:
You're running a deeply convoluted program in IDL. Your program halts
with an error. Do you:
a) Scream loudly and throw your monitor out the window?
b) Print out all the relevant IDL programs, carefully number each line
with a number 2 pencil, and draw a large frowning face next to each
offending line.
c) Stare at the IDLDE buttons unto your eye's feel funny, wondering
which level of the stack you are on.
d) Hit the control-key c,d, then up/down to move up and down the calling
stack with a nice prompt like "[-2:mypro]" to see where you are, and the
calling line highlighted. Nearby, you see a variable which is suspect.
Hit Control-c,d,p on it (or use a mouse binding -- I use shift-middle
click), and the value of that variable is printed... even if that
variable is on another calling level... ahh the magic of
routine_names()!
JD
P.S. Please don't attempt d) in the IDLDE. You may void your warranty.
|
|
|