Re: Progress report and actions

Hi John,

Just downloaded the latest draft LRM and i found the chart was
included with the correction.
I will check it but think it is correct.

Thank you and best regards,
Kaz

From: Kaz Yoshinaga <yoshi@starc.or.jp>
Subject: Re: Progress report and actions
Date: Fri, 21 Jan 2011 08:42:24 +0900 (JST)

> Hi John, all,
>
> Regarding my STARC's state chart slide,
> I put a little explanation.
>
> The slide is ment to express the simulation status along with the
> function name which triggers the state transition.
> I think this kind of the chart will help the understanding of the
> simulation (or simulator) status.
>
> It may be put on the last part of the section 5.5.8 (p.32).
>
> But I'm not sure if the presented chart is correct.
> Especially a transition from SC_END_OF_ELABORATION to
> SCSC_RUNNING through SC_START_OF_SIMULATION, and
> also SC_PAUSE to SC_END_OF_SIMULATION by event starvation.
> Hope someone can make it correct.
>
> # Also I was considering to propose the process's state chart
> # but now no time left.. (more complicated than above).
>
> Best regards,
> Kaz Yoshinaga
>
> From: john.aynsley@doulos.com
> Subject: Progress report and actions
> Date: Mon, 17 Jan 2011 19:53:39 +0000
>
>> All,
>>
>> As of Monday evening GMT, the status of the P1666 draft LRM review is:
>>
>> 92 issues raised
>> 7 issues still open...
>>
>>
>> * The semantics of immediate notifications in the presence of static sensitivity raised by David. In my opinion this is an important semantic issue, and needs to be resolved.
>>
>> * TLM-2.0 AT timing and the response exclusion rule
>>
>> * The values of the SC/TLM_IS_PRERELEASE macros: TRUE/FALSE or true/false
>>
>> * Warnings from sc_start(0) with no activity, an API to advance simulation step-by-step, and the definition of a delta cycle
>>
>> * When paused, precisely which actions should cause errors?
>>
>> * Review the STARC state chart slide
>>
>> * Spec of sc_unwind_exception
>>
>> Please study the threads on the reflector and give your feedback on each of these open issues as a matter of urgency.
>>
>> Thanks,
>>
>> John A
>>
>>
>>
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.