SC_CTHREAD in end_of_elaboration

All

[Philipp wrote]
5.4.2 end_of_elaboration (2nd enum, (d))   With the unification of SC_THREAD and SC_CTHREAD, is there still a reason to explicitly forbid SC_CTHREAD during end_of_elaboration?  It certainly works with the reference simulator.

[bpriya wrote: I won’t term it as unification of SC_THREAD, and SC_CTHREAD; the process control constructs make SC_THREADs be a superset of SC_CTHREADs, such that SC_CTHREADs could be deprecated. But as long as SC_CTHREAD is there, it is distinct from SC_THREAD, and legitimately falls under a different category. For this particular case, I don’t feel strongly, but am more inclined to retain current behavior, where SC_CTHREAD is not allowed in this callback.]

I agree with Bishnupriya, including the "I don't feel strongly" bit. Any other opinions?

John A

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