Action Items for IMs 204, 205, 214, 215

Greetings ITC techies,

I'd like to address IM 204 and 214 as per my action item from
last week. I was noticing also that IMs 205 and 215 are related
and can also be covered by this proposal so I think we can address
all 4 of these at once.

To address these IMs I've made the following updates to
the working document in section 6.1.1.

For simplicity, I'm also including the updated text here
so I can avoid another mass mailing of a large document:

----------------------- cut here -----------------------------
6.1.1 [Re: IMs 204, 205, 214, 215] Error Handling, Initialization,
and Shutdown API

SCE-MI 2 applications can continue to use the following error
handling, initialization and shutdown API functions without changes:

• SceMi::RegisterErrorHandler()
• SceMi::RegisterInfoHandler()
• SceMi::Version()
• class SceMiParameters
• SceMi::Init()
• SceMi::Shutdown()

The following rules dicate the use of these calls:

1. They are required for applications that use SCE-MI 1
    models.

2. They are optional for applications that use purely
    SCE-MI 2 models (see definitions of SCE-MI 1 vs.
    SCE-MI 2 models in section 6.2.1).

Applications with only SCE-MI 2 models that choose not to use
the error handling, initialization, and shutdown functions
above will run on any simulator that supports DPI but does not
necessarily support the SCE-MI standard.

[Informative]
This tells a nice story for compatibility of SCE-MI 2 models
with native S/W simulation environments.

-- johnS

______________________________/\/            \     \
John Stickley                   \             \     \
Mgr., Acceleration Methodologies \             \________________
Mentor Graphics - MED             \_
________________________________________________________________