Re $strobe, see also http://www.boydtechinc.com/btf/report/full_pr/559.html. Shalom > -----Original Message----- > From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On > Behalf Of Clifford E. Cummings > Sent: Friday, February 17, 2006 10:22 PM > To: sv-bc@eda.org > Subject: [sv-bc] final block and $strobe > > Hi, All - > > This sort of came up with the function-fork-join discussion. > > The $strobe command is rather unique with functions in that it > is > permitted to call a $strobe from a function even though the > printing > statement is scheduled in the monitor-events/postponed region. > This > has always worked and I see no reason to change it. > > The $strobe in the final block is another matter. > > The final block is more or less a $finish subroutine and any > $strobe > command placed in a final block will never execute. I know. I > tried! > > I believe $strobe in a final block should force a warning that > the > command will never execute. I thought about making it an error > but > since one might want to put a $strobe inside of a function and > call > the function from the always block, perhaps a warning is more > appropriate. > > In the absence of a required warning, this will generate many > questions (like the ones I sent to a couple of EDA vendors). > > Thoughts? > > Regards - Cliff > > ---------------------------------------------------- > Cliff Cummings - Sunburst Design, Inc. > 14314 SW Allen Blvd., PMB 501, Beaverton, OR 97005 > Phone: 503-641-8446 / FAX: 503-641-8486 > cliffc@sunburst-design.com / www.sunburst-design.com > Expert Verilog, SystemVerilog, Synthesis and Verification > TrainingReceived on Sun Feb 19 01:06:31 2006
This archive was generated by hypermail 2.1.8 : Sun Feb 19 2006 - 01:08:18 PST