In reply to dave_59:
In reply to verif_learner:
Without seeing an example of what you call “clutter”, this is a very subjective question.
Many times I see debug messages left in code because they didn’t fully understand how it works and should have been removed once the code was working.
Also, interactive debugging may be an alternative to the “entering/exiting” messages people put in their tasks.
I do not agree with your statement. The `uvm_info macros offer us all the freedom we need to devlop, debug a UVM verification environment and running tests and regressions with the same code without modifying/removing code lines. For this reason we can use the UVM_VERBOSITY.
If you are removing code you might have to include additional lines after making modifications in your code.
Because the UVM_VERBOSITY is evaluated first there is no overhead in the simulation. The macro will not be executed if the verbosity is higher as specified from the command line.