Don't you effectively have this even today with the rules in 6.9: "The scope of a data type identifier shall include the hierarchical instance scope. In other words, each instance with a user-defined type declared inside the instance creates a unique type. To have type matching or equivalence among multiple instances of the same module, interface, or program, a class, enum, unpacked structure, or unpacked union type must be declared at a higher level in the compilation-unit scope than the declaration of the module, interface, or program, or imported from a package. For type matching, this is true even for packed structure and packed union types." ? Shalom > The user is bound to wonder > why it's okay to have "ifv1.vec = ifv2.vec" but not "ifv1.struc = > ifv2.struc", where the 2nd case is only illegal if the type for "struc" > is local to the interface. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Sun Jan 7 00:45:07 2007
This archive was generated by hypermail 2.1.8 : Sun Jan 07 2007 - 00:45:30 PST