comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » Re: !ERR and MPFIT

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

Re: !ERR and MPFIT [message #17887 is a reply to message #17886]

Wed, 17 November 1999 00:00

Pavel Romashkin
Messages: 166
Registered: April 1999

Senior Member

> In this case it's more of a termination condition than an error. For
> example, the user function may decide that a parameter has gotten out
> of bounds unrecoverably. I would like MPFIT to return gracefully
> rather than barfing if possible, so the user routine needs a way to
> signal MPFIT that something is wrong.

How about putting something like a conditional

message, 'Number of iterations exceeded limits'

in the user procedure, to signal MPFIT. Put no CATCH in user procedure. Then, in
MPFIT you have CATCH statment followed by a graceful return. If a parameter is
so out of bounds that user procedure signals, its unlikely you can obtain
anything meaningful from MPFIT, then why not let it quit with CATCH? No common
blocks, pointers or anything else. Fully self-contained, no conflicts due to
multiple instances running, etc.

Cheers,
Pavel

Report message to a moderator

[Message index]

		Re: !ERR and MPFIT By: Craig Markwardt on Wed, 17 November 1999 00:00
		Re: !ERR and MPFIT By: Pavel Romashkin on Wed, 17 November 1999 00:00
		Re: !ERR and MPFIT By: Craig Markwardt on Wed, 17 November 1999 00:00
		Re: !ERR and MPFIT By: Pavel Romashkin on Wed, 17 November 1999 00:00
		Re: !ERR and MPFIT By: Craig Markwardt on Wed, 17 November 1999 00:00
		Re: !ERR and MPFIT By: m218003 on Wed, 17 November 1999 00:00
		Re: !ERR and MPFIT By: davidf on Tue, 16 November 1999 00:00

Previous Topic:	Re: determining the display size (IDL)
Next Topic:	Re: Floating base widget

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 10:36:32 PDT 2025

Total time taken to generate the page: 1.28031 seconds