Re: [sv-ac] 1704, empty match, and local variable assignments

Hi Ed:

I agree with your characterization of the examples.

For (a[*0:$], v=val), the user would need to find a 
a larger subsequence that does not admit empty match
and attach the "v=val" to it.

J.H.

> X-MimeOLE: Produced By Microsoft Exchange V6.5
> Content-class: urn:content-classes:message
> Date: Tue, 6 Feb 2007 07:18:52 -0800
> Thread-Topic: [sv-ac] 1704, empty match, and local variable assignments
> Thread-Index: AcdKAFszblaVweXASTiSW+V68LKeCQAAXEog
> From: "Eduard Cerny" <Eduard.Cerny@synopsys.com>
> Cc: <sv-ac@eda-stds.org>
> X-OriginalArrivalTime: 06 Feb 2007 15:18:54.0212 (UTC) FILETIME=[1D1C1C40:01C74A02]
> 
> John,
> 
> Yes, this is what I meant.
> 
> Therefore, the expression
> 
> (a, v=3Dval)[*0:$]
> 
> is OK, but
> 
> (a[*0:$], v=3Dval)=20
> 
> would be illegal. Correct?
> 
> ed
> 
> > -----Original Message-----
> > From: John Havlicek [mailto:john.havlicek@freescale.com]=20
> > Sent: Tuesday, February 06, 2007 10:06 AM
> > To: Eduard.Cerny@synopsys.COM
> > Cc: john.havlicek@freescale.com
> > Subject: Re: [sv-ac] 1704, empty match, and local variable assignments
> >=20
> > Ed:
> >=20
> > I don't think it is necessary.  I like the following:
> >=20
> >     It is illegal to attach a sequence_match_item to a sequence that
> >     admits an empty match.
> >=20
> > There will need to be some analogous statement in 17.8 to prevent
> > local variable assignments from being attached to sequences that=20
> > admit empty match.
> >=20
> > J.H.
> >=20
> >=20

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