Shalom,
I agree with you that the current LRM makes no difference between
module and macro module.
Macro Modules (as the name suggests to each of us) could have the
useful semantics of not introducing hierarchy. Whether they are
inlined or not that is another matter, because they could be inlined
and still preserve hierarchy, i.e. objects decalred inside the macro
module could be referenced by an external reference by using the
instance name of the macro module or by just using the object:
top.inst1.macro_inst1.obj vs top.inst1.obj.
By not introducing hierarchy the user helps the tool save some space
to store that hierarchy, because the user knows that no name conflict
will arise (conflict which will be reported by the tool if it occurs).
My impression is that tools other than simulators made already use of
this.
So, this could be an enhancement request with little or no problems
regarding compatibility with existing code because I doubt that there
are external references into the instance of a macro module.
Regards,
Alec
Received on Wed Jun 23 09:48:46 2004
This archive was generated by hypermail 2.1.8 : Wed Jun 23 2004 - 09:48:58 PDT