RE: [sv-ec] disabling fork join threads under task

I believe that a fork/join_none+any would fall under the list: "The
results of the following activities that can be initiated by a task are
not specified if the task is disabled". An NBA is one of those
activities on the list, making the disabling of a named block of limited
use. The reason for not specifying the result was because the committee
could not reach consensus.

I doesn't make sense to me to spend the effort to make something
explicitly unclear.

> -----Original Message-----
> From: owner-sv-ec@server.eda.org [mailto:owner-sv-ec@server.eda.org]
On
> Behalf Of Steven Sharp
> Sent: Tuesday, July 07, 2009 10:40 AM
> To: sv-ec@server.eda.org; daniel.mlynek@aldec.com
> Subject: Re: [sv-ec] disabling fork join threads under task
> 
> I agree that this is unclear.  I filed Mantis 219 on this back in
2004.
> It hasn't gotten attention, perhaps because most people think you
should
> be switching to the newer "disable fork" construct.
> 
> Even if someone thinks that the behavior of this simple example is
covered
> by the LRM text, I can come up with more complex examples that are
less
> clear, and might cast doubt on their argument for this example.
> 
> Steven Sharp
> sharp@cadence.com
> 
> 
> --
> 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.