>> >>I'm trying to understand better what a ref obj is. In >>looking over the diagrams, I noticed that a ref obj >>is connected to the vpiParent relation in a couple of >>different ways. >> >>-- In 32.26, what does it mean for a ref obj to be >>a vpiParent of a task or function declaration? >> >>> The idea behind this parent object was this : module m() ; int1 i1() ; child c1(i1.modport1); here assueme that int1 is an interface with modport1 being one of it's modport. In this scenario, the highconn of a port of c1 is i1.modport1, which will be considered as a RefObj where the type is ModPortRefobj and when you do a parent, it will give you i1, whichis again a refObj with type = vpiInterfaceRefObj. Please note that this was the case when we started thining about the Refobj initially. We have to review this and decide. - Thanks, Tapati >-- > >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 ( ) >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! *** > > Tapati BasuReceived on Thu Apr 14 12:04:53 2005
This archive was generated by hypermail 2.1.8 : Thu Apr 14 2005 - 12:05:13 PDT