Hi Ed: I don't think we are complicating anything. I think that the preponed value of an expression in the time 0 slot is already defined by the scheduling algorithm. So you should be able to delete this text entirely and just say that for _every_ time slot, a call to $sampled in that time slot returns the preponed value of its argument in that time slot. If you say that in the time 0 slot $sampled follows a different rule, then that is complicating things. Try this thought experiment. Suppose that there is an expression e that combines some static variables with declaration assignments. Suppose that no assignment in the time 0 slot changes these variables. Should a call to $sampled(e) in the time 0 slot yield a different result than a call to $sampled(e) in the time 1 slot? My opinion is "no". J.H. > X-MimeOLE: Produced By Microsoft Exchange V6.5 > Content-class: urn:content-classes:message > Date: Thu, 25 Jan 2007 13:43:00 -0800 > Thread-Topic: [sv-ac] reminder to vote on mantis 1550 > Thread-Index: AcdAxdG186prUgy2SBOcNKMORR/kCAAA4F8A > From: "Eduard Cerny" <Eduard.Cerny@synopsys.com> > Cc: <sv-ac@eda-stds.org> > X-OriginalArrivalTime: 25 Jan 2007 21:43:01.0498 (UTC) FILETIME=[C967DDA0:01C740C9] > > Hi John, > > This is exactly what I wanted to avoid, having to evaluate the > expression based on the initial assigned and default values. I.e., in > the case of an expression, just use the default value of its type. But > if the majority thinks that it is more appropriate to do wht you > suggest, fine. But we are here dealing with a corner case, because in > most applications, a disable iff or $assertoff takes care of time 0. Is > it worth complicating it? > > ed > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Jan 25 17:14:27 2007
This archive was generated by hypermail 2.1.8 : Thu Jan 25 2007 - 17:14:45 PST