So maybe that particular restriction should be removed. Shalom > -----Original Message----- > From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On > Behalf Of Steven Sharp > Sent: Friday, February 17, 2006 4:50 AM > To: Dave_Rich@mentor.com; sv-ec@eda.org; sv-bc@eda.org; > ambar.sarkar@paradigm-works.com > Subject: [sv-bc] RE: [sv-ec] Can a function contain a > fork/join/any/none? > > > >From: "Ambar Sarkar" <ambar.sarkar@paradigm-works.com> > > >Given that we do not want functions to interact with the > >scheduler, we are in effect forbidding functions to trigger > events as well, > >correct? > > The 1364-2005 standard actually forbids event trigger > statements in > functions. This is probably because Verilog-XL doesn't allow > it. > It shows a desire to discourage the side-effect of waking up > other > processes, but doesn't actually prevent it, since you can wake > up > another process from a function by writing to a variable. > > > > Steven Sharp > sharp@cadence.comReceived on Fri Feb 17 02:08:45 2006
This archive was generated by hypermail 2.1.8 : Fri Feb 17 2006 - 02:09:01 PST