Info reporting in SCE-MI

From: Shabtay Matalon <shabtay@cadence.com>
Date: Wed Mar 24 2004 - 17:31:11 PST

The SceMiEC *ec argument allows the caller of any SCE-MI class to determine if errors will be conveyed to the caller by using the non-NULL pointer or to an error handler by using the NULL pointer (either the default error handler or the one that was registered).

However, if I properly understood section 5.3.2.2 that deals with the SceMiIC class, info type messages cannot be controlled to go back to the caller and will only be conveyed to an info handler, either the default error handler or the one that was registered.

If I further look at which types of errors and information is provided in each case, the error handling facility is stated to support "irrevocable errors" and thus the non-Null pointer option is of little use as the application needs to report the error and abort.

To the contrary, as the info type messages should be handled at the discretion of each caller, I would have expected that the caller would receive the info type messages and thus the non-Null pointer option will be of higher value if applied to info type messages. In particular this is useful given the 3 enumerations of info types that the caller may branch upon given the context of the call.

Have I misunderstood the intended use of these classes?

Can one explain the current logic behind providing the non-NULL pointer option for irrevocable errors and not for info handling? Is this an issue worth reconsidering for amending in the spec?

Thanks,

Shabtay

-------------------------------------

Shabtay Matalon
Solution Architect
Solutions R&D, SFV
Phone: (408) 428 5081
email: shabtay@cadence.com
Received on Wed Mar 24 17:31:12 2004

This archive was generated by hypermail 2.1.8 : Wed Mar 24 2004 - 17:31:13 PST