Users are expecting packages to contain interface declarations, and are surprised when told that the LRM disallows that. Conceptually, users seem to lump interface declarations together with typedefs and class declarations, perhaps because an interface-type port declaration can specify the name of an interface in place of the generic 'interface' keyword. (However, unlike with classes, a particular specialization of the interface cannot be specified in a port declaration.) Why does the LRM disallow interface declarations in packages? If there's not some serious principle forcing this restriction, user demand indicates that the restriction should be lifted. -- BradReceived on Fri Apr 28 08:48:19 2006
This archive was generated by hypermail 2.1.8 : Fri Apr 28 2006 - 08:48:26 PDT