disable and the Initiialization Phase

Bishnupriya,

The revised spec says:

"Disabling a process before simulation has started (e.g., from one of the
callback phases), or before the process has executed for the first time,
shall have the following behavior:
? If the process was declared with dont_initialize(), then the
disable shall take effect immediately, and the process shall not be
eligible to run again until it is enabled
? If the process was not declared with dont_intialize(), then that
implies the process has already been scheduled to run for the first time,
and the disable shall take effect only after the first default execution
of the process "

That I don't like! LRM 4.2.1.1 says that processes are made runnable
during the initialization phase, which occurs after elaboration. If a
process is disabled during elaboration, I see no reason why it should
execute during initialization. That would seem to contradict the rule that
a process cannot get added to the set of runnable processes while it is
disabled (Scheduling Insights para 3).

John A

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