I just noticed that 36.14 in Draft 4 has the following: Details: 1) A ref obj represents a declared object or sub-element of that object that is a reference to an actual instantiated object. A ref obj exists for ports with ref direction, for an interface port, a modport port, or for formal task function ref arguments. The specific cases for a ref obj are: - A variable, named event, named event array that is the lowconn of a ref port - Any subelement expression of the above - A local declaration of an interface or modport passed through a port or any net, variable, named event, named event array of those - A virtual interface declaration in a class definition - A ref formal argument of a task or function, or sub-element expression of it A ref obj may be obtained when walking port connections (lowConn, highConn), when traversing an expression that is a use of such ref obj, when accessing the virtual interface of a class, or when accessing the io decl of an instance or task or function." Is there any conflict with the text of Mantis 2235? Thanks, Shalom Mantis 2235 adds to 13.5.2, "Only the following shall be legal to pass by reference: * a variable * a member select of a class property or a member of an unpacked structure * a non-slice indexed select of an unpacked array. Nets and selects into nets shall not be passed by reference. " --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Apr 3 04:53:26 2008
This archive was generated by hypermail 2.1.8 : Thu Apr 03 2008 - 04:54:17 PDT