[sv-ec] iff construct in SV coverage: does it take precedence over coverpoint expression?

An interesting situation concerning iff in coverage encountered by one
of our consultants. The LRM goes to gret pain to specify guards for
constraints, but not covergroups. It is not entirely unreasonable to
expect the iff to be evaluated before attempting to evaluate the
coverpoint expression:

I have a coverpoint that looks like this:

my_coverpoint : coverpoint ingress_trans.data iff (X == 1 && Y == 1);

The following scenario errors (but I don't think it should):

ingress_trans == NULL
X != 1
Y != 1

Since the iff statement should evaluate to FALSE, I'd expect this
coverpoint to be ignored.  But, since ingress_trans is NULL, I get a
runtime error.  However, the ignoring seems to work ok when
ingress_trans is NOT NULL.  Is this the intended functionality of the
iff construct?

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.