Re: Convert from free to fixed

On 2010/10/4 6:32 PM, Larry Ducie wrote:

...
The line would already be in error. The assignment has failed and the condition handler has been called.

I would put a breakpoint on the line after this line, tell the condition handler to continue and then fix up the data post-facto.

Let me see if I understand correctly. Your conditional handler would normally percolate or promote the exception, and it would have only resume at next instruction when you set the action parameter to 10 within a debug session? And you would never set the action parameter to resume unless you were able to set a breakpoint on the next statement following the statement in error?

That seems ok to me.

I can see why you'd only do that rarely. It's not always easy to find the next statement. For example when the error statement is an IF statement, you wouldn't know whether the next statement is going to be in the "if" part or or the "else" part. It might be a good idea to both set your breakpoint where you think the next statement is, and also use the "step outof" command in the debugger.

As a rule of thumb, I'd say that a CEEHDLR condition handler should be _coded_ so that it always returns with the action parameter being either percolate or promote. So having it return with action being set to resume would only be possible in a debug setting.