uvm:9.2.2 Small and beautiful and factory mechanism of overloading

1. Small and beautiful and factory mechanism of overloading

2. The drive_one_pkt of the original a_driver are as follows:

1) divided into 3 sub-tasks.

2) If you want to construct an example of a SFD error, you only need to derive b_driver from A_driver and overload the DRIVE_SFD.

3. If it is not divided into 3 sub-tasks, it is a complete task:

1) Then the task that needs to be overloaded in B_driver is the whole drive_one_pkt:

At this point, the code for the other two sub-functions is copied to the DRIVE_ONE_PKT, which is prone to errors. The code is reusable and can be encapsulated as an overloaded function/task or class.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

uvm:9.2.2 Small and beautiful and factory mechanism of overloading