RE: [sv-ec] FW: [sv-bc] Can a function contain a fork/join/any/none?

Dave,

> 1. The proposal was updated on Nov-27 to remove the word 'mature"

[SB] Yes, I know. You changed it to,
"A function that tries to schedule an event that will become active only
after that function returns shall be an error in any context in which a
side effect is disallowed or in any context other than procedural code
originating in an initial or always block."

That still does not answer my question,
> > Do nonblocking assignments and procedural continuous assignments
fall
> > into that category (maturing after return)?

Thanks,
Shalom


> > The proposal allows, among other things, nonblocking assignments and
> > procedural continuous assignments in functions, which were not
allowed
> > till now.
> >
> > 1. The proposal also says,
> > "A function that schedules an event to mature after that function
> > returns shall be illegal in any context in which a side effect is
> > disallowed or in any context other than procedural code originating
in
> > an initial or always block."
> >
> > I already mentioned that the term "mature" needs to be defined.
> > Do nonblocking assignments and procedural continuous assignments
fall
> > into that category (maturing after return)?