1. ► cbReadWriteSync callbacks are called before cbReadOnlySynch callbacks.

2. ► Even Driven Simulation cannot simulate combinational circuits.

3. ► In s_cb_data, the cb_rtn field is used to provide the function pointer which will be called when the callback event happens.

4. ► In C++ callbacks are implemented using object pointers.

5. ► Incorrectly written VPI applications may leak memory.

6. ► Depth-first walk is more useful than a breadth-first walk.

7. ► VPI provides routines using which one can easily traverse over design graph.

8. ► vpiSysTfCall returns the handle to the task or function call which occurred in Verilog and in turn called this C/C++ routine.

9. ► Iterators obtained using vpi_iterate can be rewinded using VPI routines.

10. ► Stimulus for simulation must always be in the form of binary data i.e. 0’s and 1’s.

11. ► A Verilog design is internally represented in the form of a graph where edges represent the connectivity.

12. ► In-order depth-first walk is defined for all kinds of trees.

13. ► vlog_startup_routines is a function which is called by simulator to register routines.

14. ► In s_cb_data, the obj field is used to point to the handle on which the callback is registered.

15. ► Verilog compiler can detect output mistmatch between Verilog and ‘C’ land when routine is exported as a function.