+ /*!
+ * \brief associatedIface the control (resp. data) interface that is bounded to this data (resp. control) interface
+ * If a reference block is designed to be fully integrated in Blast, nearly every data interface is bounded
+ * to a control interface that signals if the value presented on the interface is valid or not. associatedIface
+ * references this control interface if this is a data interface, and a data interface is this is a control interface.
+ * Note that the association is done by the call of setAssociatedIface() that must be done only for a control interface.
+ * (NB: a test is done in the method to prevent the other case).
+ */
+ AbstractInterface* associatedIface;
+ /*!
+ * \brief clkIface represents the clock interface that is used in processes modifying this interface. It is only relevant for
+ * Data interfaces and clock outputs (that comes from a clkrstgen). Since Control interfaces are automatically associated to a
+ * Data interface, clkIface is "" for them. Wishbone interfaces
+ * In general, blocks have a single
+ * clock interface which is by default automatically connected to the main clock dispatched by the clkrstgen block in top group.
+ * Nevertheless, the designer has the possibility to connect the block taht owns this interface to another clkrstgen block. Moreover,
+ * some blocks may have several clocks, e.g. dual port RAMs, FIFOs.
+ */
+ QString clkIfaceName;
+ int clkIfaceType; // 0 for not affected, 1 for clock input name, 2 for user param name
+
+