The existing restriction against non-integer types made the other
restrictions (like string, event) redundant as they were already
non-integer types. By removing the restriction against non-integer
types, you are opening up the door to unmentioned and yet to be defined
additional types.
A better way to describe this is similar to the restrictions on event
and constraints expressions. You can use any type in an expression as
long as the result is an integral type. That means if you want to use a
real variable in an assertion, you must either cast it to an integral
value, or compare it using a recreational/equality operator to yield an
integral result.
There are already restriction on reference members of classes in
non-procedural contexts, but there should be nothing wrong with
asserting (class_handle != null)
Dave Rich
Verification Technologist
Mentor Graphics Corporation
New Office Number: 510-354-7439
<http://www.twitter.com/dave_59> <http://go.mentor.com/drich>
-- 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 : Thu Sep 30 2010 - 12:11:53 PDT