Note that 1364-2005 says, "An event is not made to occur by changing the index of an event array in an event control expression." Shalom > -----Original Message----- > From: owner-sv-ec@server.eda.org [mailto:owner-sv-ec@server.eda.org] On > Behalf Of Steven Sharp > Sent: Wednesday, September 13, 2006 12:04 AM > To: sv-ec@server.eda-stds.org; Dave_Rich@mentor.com > Subject: Re: [sv-ec] Arrays of events > > > >From: "Rich, Dave" <Dave_Rich@mentor.com> > > >Is this simply a BNF oversight or is this an intentional omission. > Seems > >to me that if you can declare an array of events, you should be able to > >trigger an element of an array. > > I don't see any possible use for an array of events if you can't trigger > one of them. > > BTW, there are some issues with arrays of events that were not > considered > when they were added in 1364. They appear because of the possibility > that > the event referenced by an array reference could change if the value of > the index changes. The same issue occurs in 1800 with the ability to > assign an event to another event. You have to define what it means to > wait on an event in that situation. There is no analog in the rules for > other things in event controls, because those are based on whether the > value changed, and named events do not have values. > > Steven Sharp > sharp@cadence.comReceived on Wed Sep 13 02:08:26 2006
This archive was generated by hypermail 2.1.8 : Wed Sep 13 2006 - 02:08:30 PDT