Francoise,
nice work, thanks a lot. Some minor remarks:
a) You might want to change the second define to
vpiMultiAssignmentPatternOp :-)
b) I believe the addition to the note 5) should read "...
vpiAssignmentPatternOp and vpiMultiAssignmentPatternOp ..." instead of
"... vpiAssignmentPatternOp or vpiMultiAssignmentPatternOp ...", but I
am not a native english speaker
c) For the sake of clarity I would ask for representing a real 0 by 0.0
in all examples
Regards,
-Michael
Francoise Martinolle wrote:
> 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
> '
>
>
>
>
>
-- NOTE: The content of this message may contain personal views which are not neccessarily the views of Freescale, unless specifically stated. ___________________________________________________ | | _ | Michael Rohleder Tel: +49-89-92103-259 | _ / )| Freescale Semiconductor Fax: +49-89-92103-680 |( \ / / | Freescale Halbleiter Deutschland GmbH | \ \ _( (_ | _ Schatzbogen 7, D-81829 Munich, Germany _ | _) )_ (((\ \>|_/ > < \_|</ /))) (\\\\ \_/ / mailto:Michael.Rohleder@freescale.com \ \_/ ////) \ /_______________________________________________\ / \ _/ \_ / / / \ \ The information contained in this email has been classified as: General Business Information (x) Freescale Internal Use Only ( ) Freescale Confidential Proprietary ( ) *** This note may contain Freescale Confidential Proprietary or Freescale Internal Use Only Information and is intended to be reviewed by only the individual or organization named above. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination or copying of this email and its attachments, if any, or the information contained herein is prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. Thank you! ***Received on Thu Feb 10 06:41:22 2005
This archive was generated by hypermail 2.1.8 : Thu Feb 10 2005 - 06:41:38 PST