Hi Forum,
Within UVM classes uvm_report_server and uvm_factory there exist functions set_max_quit_count and set_type_override_by_type respectively.
The last argument in these APIs are bit overridable=1 and bit replace=1 which provide flexibility to user whether further calls to these APIs should override the previous calls.
If user has multiple calls to uvm_config_db#(int)::set from same level of hierarchy / precedence, the last write wins during uvm_config_db#(int)::get
Does UVM have any such feature to ensure that a specific write always wins ( even if there are further calls to write using same precedence ) ?
As Dave commented in thread ::
It might help to think of a list of strings pushed to the front of a queue for every call to set(). Then each call to get() scans the queue from front to back to find a string match with the scope name provided with the get.
Is it possible that calls to set() by default pushes to back of the queue and a specific write pushes to the front of the queue ?
Thanks in Advance