Differences

This shows you the differences between two versions of the page.

--- intro_example:namespace [2020/06/19 11:25] – [Creating a library of building blocks] rajit
+++ intro_example:namespace [2025/05/17 11:51] (current) – [Creating a library of building blocks] rajit
@@ Line 7: / Line 7: @@
 (a) For simple projects, design files containing building blocks can be imported using keyword ''import''. For example, the ''gates.act'' file contains basic logic gates.
-<code>
+<code act>
 defproc nand2 (bool? a,b; bool! y)
 {
@@ Line 36: / Line 36: @@
 This file can be imported in a new ACT file ''xor2.act'' for creating XOR gate using basic logic gates.
-<code>
+<code act>
 import "gates.act";
@@ Line 54: / Line 54: @@
 The following example creates a namespace gates in file ''gates.act'' and defines process for basic logic gates within the namespace.
-<code>
+<code act>
 namespace gates
 {
@@ Line 86: / Line 86: @@
 }
 </code>
+Note the use of the ''export'' keyword. By default, anything defined in a namespace is only visible within the namespace; it must be explicitly ''export''ed for it to be visible outside the namespace.
 As shown below, this library is imported in a new ACT file ''adder.act'' to design full adder using logic gates defined in the library.
-<code>
+<code act>
 import "gates.act";
@@ Line 102: / Line 104: @@
 }
-adder FA;
+adder fa;
 </code>
@@ Line 108: / Line 110: @@
 Finally, ACT supports another import format that is similar to those provided by object-oriented languages like Python and Java. Since ''gates.act'' defines the namespace ''gates'', it can be imported as follows:
-<code>
+<code act>
 import gates;
@@ Line 121: / Line 123: @@
 }
-adder FA;
+adder fa;
 </code>
 The ''import'' statement looks for ''gates.act'' (details are in [[language:namespaces|Namespaces]]), and imports it if it is found. It also checks that the namespace ''gates'' exists after the import.
+Finally, if you are going to be using the ''gates'' namespace a lot, it can be added to the search path used to find type definitions as follows.
+<code act>
+import gates;
+open gates;
+defproc adder (bool? a,b,ci; bool! s,co)
+{
+  bool y1,y2,y3;
+  xor2 X1(a, b, y1);
+  and2 A1(a,b,y2);
+  xor2 X2 (y1,ci,s);
+  and2 A2(y1,ci,y3);
+  or2 O1(y2,y3,co);
+}
+adder fa;
+</code>
 ===== Simulating with prsim script =====
 Run simulation in prsim with script as:
 <code>
-prsim adder.act < adder.scr
+$ aflat adder.act > adder.prs
+$ prsim adder.prs < adder.scr
 </code>
@@ Line 135: / Line 160: @@
 <code>
-prsim adder.act
+$ prsim adder.prs
 (Prsim) source adder.scr
 </code>