[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Catch problem
- Subject: Re: Catch problem
- From: Ben Tupper <btupper(at)bigelow.org>
- Date: Tue, 02 Jan 2001 13:27:01 -0500
- Newsgroups: comp.lang.idl-pvwave
- Organization: Bigelow Laboratory for Ocean Sciences
- References: <92t5f7$ejp$1@mercury.wright.edu>
- Xref: news.doit.wisc.edu comp.lang.idl-pvwave:22790
Howdy,
I have done this all too frequently, Add ...
CATCH, /CANCEL
inside the if statement block so that the Error_Status value reverts to 0
(zero) before exiting the block. Error catching seems like big brother
watching to me... unlike the most of the procedures I know (maybe with the
exception of XMANAGER) where the action is history once the command is
given, CATCH keeps right on catching.
Ben
ALAN FRAZIER wrote:
> Recently, I started learning the catch procedure to help with some error
> checking. I typed the code word-for-word out of the IDL 5.3
> documentation:
>
> PRO ABC
>
> A = fltarr(10)
>
> CATCH, Error_status
>
> IF Error_status NE O THEN BEGIN
> PRINT, 'ERROR INDEX: ', Error_Status
> PRINT, 'ERROR MESSAGE: ', !ERR_STRING
> A = FLTARR(12)
> ENDIF
>
> A[11] = 12
>
> HELP, A
>
> END
>
> to help me learn this command. However, this code does not seem to
> execute correctly. As far as I can tell, the code causes some sort of
> infinite loop on the if statement. Any ideas what I am doing wrong? I am
> using IDL 5.4 on a Mac.
>
> --
> Alan
--
Ben Tupper
Bigelow Laboratory for Ocean Sciences
180 McKown Point Rd.
W. Boothbay Harbor, ME 04575
btupper@bigelow.org