PR# 15266 Failure to write to stdout in web app raises exception with code 21 instead of 27
Problem Report Summary
Submitter: prestoat2000
Category: EiffelWeb
Priority: Medium
Date: 2009/01/13
Class: Support
Severity: Serious
Number: 15266
Release: 6.3.76070
Confidential: No
Status: Closed
Responsible:
Environment: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.8.1.13) Gecko/20080328 Firefox/2.0.0.13
Solaris 10 on SPARC
Synopsis: Failure to write to stdout in web app raises exception with code 21 instead of 27
Description
We just upgraded from Eiffel 5.7 to 6.3. We're getting a failure in a web
application. A failure to write to stdout in a web app used to raise an
exception with code 27 (runtime_io_exception) but now raises an exception with
code 21 (io_exception). This causes our application to no longer rescue
the exception, so it sends us e-mail indicating a problem. This typically
happens when the user cancels a download in the browser.
We can make code changes to deal with this, but I wanted to verify that this
is intentional. I noticed the following in class ISE_EXCEPTION_MANAGER
type_of_code (a_code: INTEGER): ?TYPE [EXCEPTION]
-- Exception type of `a_code'
do
inspect a_code
...
when {EXCEP_CONST}.Runtime_io_exception then
Result := {IO_FAILURE}
So runtime_io_exception and io_exception seem to have been merged.
Is this intentional?
To Reproduce
Problem Report Interactions