-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
import/export declaration #59
Comments
Visibility of items imported by import declarations outside module declarations is global. // foo_pkg.sv
package foo_pkg;
localparam FOO = 0;
endpackage // foo_0.sv
import foo_pkg::*;
module foo_0;
localparam FOO_0 = FOO;
endmodule // foo_1.sv
module foo_1;
localparam FOO_1 = FOO;
endmodule Therefore, I think import declarations should be inside a module declaration. |
There are three ideas.
to module ModuleA import PackageA::*;
endmodule
module ModuleB import PackageA::*;
endmodule This case disallows global import like SV.
to module ModuleA import PackageA::*;
endmodule In this case all imports in a module move to the module header. |
I think
I think this is not a problem because large scope has bad influence. |
module's import like below causes parsing and formatting complexity.
Instead of supporting module's import, is it sufficient like below?
The text was updated successfully, but these errors were encountered: