Hi folks, I've attached my updated proposal. The only change I've made is to the first sentence in the CHANGE to 7.4.2. I don't seem to be able to attach this to the Mantis, probably because it's currently in the resolved state. --Mike Michael Burns wrote: > > I agree this is somewhat confusing; this might be because I was > confused when I wrote it... > > By "variable data types", I meant those data types which are allowed > for variable declarations. However, as Dave points out this is > meaningless, since variables can be of any data type. My mistake was > in thinking that arrays "contain" nets or variables. I would prefer > that the sentence in 7.4.2 be much more like the original text: > > "Unpacked arrays can be made of any data type." > > This section is only describing the unpacked array _type_; any > additional restrictions due to storage class ought to be described in > the definition of that storage class (as you both point out, in 6.6). > > --Mike > > Bresticker, Shalom wrote: >> Dave, >> I agree with you that this part of the proposal is worded in a >> confusing way. But regarding 6.6, we already made that change in >> Mantis 2092. A sentence could be added to 7.4.2 like, "However, net >> arrays shall have a fixed-size (see 6.6)." >> Note that even net fixed-size arrays can not have all data types. For >> example, 2-state data types and reals are not allowed. >> Shalom >> >> >> ------------------------------------------------------------------------ >> *From:* owner-sv-ec@server.eda.org >> [mailto:owner-sv-ec@server.eda.org] *On Behalf Of *Rich, Dave >> *Sent:* Sunday, February 03, 2008 8:05 PM >> *To:* sv-ec@server.eda.org >> *Subject:* [sv-ec] question mantis 1447 >> >> I am reviewing the revised sentence in section 7.4.2 of the >> proposal: “Unpacked fixed-size arrays can be made of any data >> type, and whereas dynamic arrays, associative arrays and queues >> can only be made of variable data types.” >> >> The use of the word “variable” is confusing on a few accounts: >> >> 1. “Variable” is the antonym of “fixed,” and quickly read, >> makes me think that you are trying to restrict dynamic >> arrays to being made up of variable-sized elements >> 2. The data types allowed for group of data storage called >> /Variables/ is un-restricted, whereas the data types allowed >> for group of data storage called /Nets/ is restricted, so >> what is being restricted here? >> 3. It’s not possible to specify the element type of an array as >> belonging to /variables/ or /nets/. >> >> May I suggest making a friendly amendment and leaving that >> sentence in its original form, an making a small modification in 6.6 >> >> Certain restrictions apply to the data type of a net. A valid data >> type for a net shall be one of the following: >> >> a) A 4-state integral type, including a packed array or packed >> structure. >> >> b) An fixed-size unpacked array or unpacked structure, where each >> element has a valid data type for a net. >> >> Dave >> >> David Rich >> Verification Technologist >> Design Verification & Test Division >> Mentor Graphics Corporation >> dave_rich@mentor.com >> Office: 408 487-7206 >> Cell: 510 589-2625 >> >> >> -- This message has been scanned for viruses and >> dangerous content by *MailScanner* >> <http://www.mailscanner.info/>*, and is >> believed to be clean. * >> >> *--------------------------------------------------------------------- >> Intel Israel (74) Limited >> >> This e-mail and any attachments may contain confidential material for >> the sole use of the intended recipient(s). Any review or distribution >> by others is strictly prohibited. If you are not the intended >> recipient, please contact the sender and delete all copies. >> * >> * >> -- >> This message has been scanned for viruses and >> dangerous content by *MailScanner* <http://www.mailscanner.info/>, >> and is >> believed to be clean. * > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
This archive was generated by hypermail 2.1.8 : Mon Feb 04 2008 - 13:46:29 PST