Something to bear in mind for multi-type resolution.
When you use a type for access to a net in a module, you are actually
saying something about what the type of the drivers and/or receivers
are. Since you can tell what a driver type is from context (it's the RHS
in an assignment) the type primarily refers to what the receiver type is
(which is difficult to determine from context). E.g. you may be able to
tell from context that the driver is boolean (alwyas 1 or 0, never X or
Z), but the resolved value of the net may be X or Z (which is what a
receiver would see).
This factors into how you do driver conversion/resolution, since it
would be more efficient not to do a boolean->4-state conversion if you
don't have to, so you might want to leave drivers uncoerced at the
module instance level.
Kev.
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Mar 9 11:24:52 2011
This archive was generated by hypermail 2.1.8 : Wed Mar 09 2011 - 11:24:53 PST