My view of `timescale is that it is just like any other compiler directive. It is not a statement itself, but effects the processing of certain statements that follow. In this case, it only effects the processing of the definition of the design units that follow it. I see no confusion with statements in $unit. Dave > -----Original Message----- > From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org] On > Behalf Of Steven Sharp > Sent: Thursday, June 05, 2008 2:56 PM > To: sharp@cadence.com; sv-bc@server.eda.org; shalom.bresticker@intel.com > Subject: RE: [sv-bc] merge error on timescale > > > >From: "Bresticker, Shalom" <shalom.bresticker@intel.com> > > >So now what about tasks that are declared in %unit? > > They have problems similar to those for packages. They are worse > because a `timescale at the start of the source will not affect them, > so this situation is more likely to arise. However, I think that > requiring them to have a timescale (if any design elements do) would > also cause a problem. > > Add this to the list of disadvantages of the compilation unit as > compared to packages. > > 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.Received on Thu Jun 5 15:40:47 2008
This archive was generated by hypermail 2.1.8 : Thu Jun 05 2008 - 15:41:31 PDT