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

This raises the question "Does a package exist if no one imports it?"
Having static space allocated by an unused package is not usually an
issue, but if it creates threads, I can see that as being a problem. I
vaguely remember this as the reason that modules and continuous
assignments were not allowed in packages. 

> -----Original Message-----
> From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of
Steven
> Sharp
> Sent: Thursday, February 23, 2006 12:24 PM
> To: sharp@cadence.com; sv-ec@eda.org; sv-bc@eda.org;
> Arturo.Salz@synopsys.com
> Subject: RE: [sv-ec] RE: [sv-bc] Can a function contain a
> fork/join/any/none?
> 
> 
> >[Arturo]
> >My point is that all of these issues exist in other contexts and the
> >tools must be able to deal with them. By extension, these do not
> >represent any fundamental or implementation problem.
> 
> But Dave has pointed out that this allows some things that are not
> possible with functions triggering other processes, or with tasks.
> In particular, it allows creating a thread whose parent is a
> variable initialization.  This in turn means it has allowed root
> threads to be created in a package, which could not happen before.
> 
> I don't know what specific problems Dave is concerned this will cause.
> 
> Steven Sharp
> sharp@cadence.com