Subject: Re: [sv-bc] Separate Compilation Meeting Monday 6/9/03
From: Kevin Cameron (sv-xx@grfx.com)
Date: Wed Jun 18 2003 - 10:28:52 PDT
> From: Adam Krolnik <krolnik@lsil.com>
>
> Hi Randy;
>
> On the surface, namespaces look like modules. It may be helpful in analyzing
> this to see a comparison between modules and namespaces.
Good point. What is the difference between nesting in a module and nesting
in a namespace? - personally I didn't think the module nesting was particularly
functional, maybe if you add the namespace semantics it will work sensibly
[without anther keyword :-) ].
> You also write that import statements outside a module or scope will affect subsequent
> module or interface scopes.
>
> Do import statements only have file scope? Or could one import something for the first
> file and have subsequent files obtain the effects of the import?
>
> I presume they have file scope. Thus for files with multiple modules one import is
> sufficient.
>
> For the import statement, why would it be necessary to say
>
> import Myspace.*;
>
> Other languages (such as Perl) only require reference to the name to import all
> the definitions:
>
> use Getopt::Long; # Get all definitions
>
> import Complex; // Get all verilog complex math functions.
An import statement in Perl would cause the interpreter to go find the module
and load it - what's the implication for SV? - are you assuming the namespace
is already defined (in a header)?
Kev.
> Can one import a wire/net declared in the namespace? What does this mean? a wire
> that is shared by all modules importing it? What does it mean if you import a
> wire but are not in a module scope? in a named scope?
>
>
> Thanks.
>
> Adam Krolnik
> Verification Mgr.
> LSI Logic Corp.
> Plano TX. 75074
>
This archive was generated by hypermail 2b28 : Wed Jun 18 2003 - 10:30:07 PDT