Project

General

Profile

Feature #4352

finish progress.lang.apperror and progress.lang.syserror

Added by Constantin Asofiei over 4 years ago. Updated almost 2 years ago.

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

100%

billable:
No
vendor_id:
GCD

Related issues

Related to Base Language - Feature #3751: implement support for OO 4GL and structured error handling Closed
Related to Base Language - Feature #4373: finish core OO 4GL support New
Related to Base Language - Bug #5761: replace ErrorManager.displayError with recordOrThrowError and fix recordOrShowError to morph into a recordOrThrowError in certain cases. New
Related to Base Language - Bug #4602: fixes for OO 4GL and structured error handling New

History

#1 Updated by Constantin Asofiei over 4 years ago

  • Related to Feature #3751: implement support for OO 4GL and structured error handling added

#2 Updated by Constantin Asofiei over 4 years ago

apperror vs syserror - these weren't tested comprehensively, the support is pretty good, but when combined with ROUTINE-LEVEL or BLOCK-LEVEL statements, we may have missing issues (as I recall, we need to convert ERROR condition to SysError class). AppError is used at least by RETURN ERROR statements.

We need to test and fix any deviations.

This will complete both ON THROW and UNDO THROW.

#3 Updated by Greg Shah over 4 years ago

#4 Updated by Greg Shah over 2 years ago

  • Related to Bug #5761: replace ErrorManager.displayError with recordOrThrowError and fix recordOrShowError to morph into a recordOrThrowError in certain cases. added

#5 Updated by Greg Shah almost 2 years ago

  • Related to Bug #4602: fixes for OO 4GL and structured error handling added

#6 Updated by Greg Shah almost 2 years ago

  • % Done changed from 0 to 100
  • Status changed from New to Rejected

The work for this is included in #4602.

Also available in: Atom PDF