Project

General

Profile

Bug #9192

FWD defines multiple top level exceptions

Added by Artur Școlnic almost 2 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
15444
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Artur Școlnic almost 2 years ago 

block-level on error undo, throw.
def var h as handle.

repeat: 
   h = h:next-sibling.
  catch ex as progress.lang.error:
     message ex.
   end.
end.

repeat: 
   h = h:next-sibling.
   catch ex as progress.lang.error:
      message ex.
   end.
end.

message ex.  // only one 'ex_top' should be 'promoted' and defined in FWD

In the converted code:
@LegacySignature(type = Type.VARIABLE, name = "ex")
   object<? extends com.goldencode.p2j.oo.lang.LegacyError> ex_top = TypeFactory.object(com.goldencode.p2j.oo.lang.LegacyError.class);

   @LegacySignature(type = Type.VARIABLE, name = "ex")
   object<? extends com.goldencode.p2j.oo.lang.LegacyError> ex_top_1 = TypeFactory.object(com.goldencode.p2j.oo.lang.LegacyError.class);

FWD defines one top level exception per repeat block, instead of just one for the whole program.

#3 Updated by Artur Școlnic almost 2 years ago

This ticket originated from #8980-43.

Also available in: Atom PDF