A couple of notes:
i) I added 2 defined constants to represent the assignment pattern
and the multi assignment pattern.
This is parallel to the concat and multiConcat.
ii) I think that in the future we could enhance the class "pattern" to
represent the index,
member, type or default keys. We could add an iteration vpiPattern available
from a
vpiAssignmentPatternOp operation. I am not completely sure presently what
does the pattern
class represents (it has to do with case pattern matching and condition
pattern
matching and so I do not want to rush into a proposal. Today the pattern
class is either
an expression, any pattern a struct pattern or a tagged pattern. The struct
pattern corresponds
to a member key association. The tagged pattern corrsponds to a tagged
member of a tagged union,
the any pattern correspongs to a .* match.
With a little more of understanding on how the pattern matching is
represented in VPI,
I would be able to make a proposal, but what I have proposed in the uploaded
document
is acceptable for the moment...
Francoise
'
Received on Wed Feb 9 19:46:21 2005
This archive was generated by hypermail 2.1.8 : Wed Feb 09 2005 - 19:46:28 PST