Break only when Debugging

[Chris]

Guys,

I think the problem is not the handling of BEGIN SEQUENCE/RECOVER statements. The problem is that in VO, when an error happens, you can continue execution of the code that caused that problem from the next line, or you can even try to rerun the offending line of code. Or you can chose to display a dialog when an error happens, so the user becomes aware of this and for that, you do not even need to have a BEGIN SEQUENCE at all for that. I am afraid it is completely impossible to emulate anything of this in .Net, without modifying the actual code..

Chris

[wriedmann]

Hi Chris,

I know that is impossible to emulate the behaviour of VO. But adding a sort of error handler in seqences without helps at least to find the place where the error was occurring.
Of course such places have to be changed afterwards....

Wolfgang

[wriedmann]

Hi Chris,

when you have implemented NoIVarGet()/NoIVarPut() in the runtime: could you send me please also an update?
I'm relying massively on these functions in my server classes.
The same is true for all the IVar*-functions.

Wolfgang

[Chris]

Done!

[FFF]

Chris,
FTR, should we "ask" for interim-dlls or will they go automatically to the download area?

Karl

[Chris]

Hi Karl,

For now it is easier to send updates directly to those of you who report problems/ask for the fixes, because this way they can directly report back if the problem is indeed fixed, or if they see any other sideeffects, this is much safer than making general releases with not very much tested yet (so potentially breaking) updates. I guess you just asked for an update though, so I'll send you one right away

Chris

[FFF]

Hi Chris,
got it. No, actually i was only curious how the plan was. Now i'm under pressure <G>


Karl

[Chris]

Hehe!