UVM Field Macros - Positive flag

[trushali]

I was reading about UVM field macro flags and came across the following statement:

Specifying UVM_COPY with no other flags actually turns on all of the other operations (copy(), compare(), print(), pack(), unpack(), record()).

My question is: if specifying UVM_COPY alone effectively enables all operations, then what is the purpose of defining positive flags such as UVM_COPY, UVM_COMPARE, UVM_PRINT, etc.?

In what situations are these positive flags intended to be used? Are they mainly meant to be combined with other flags (e.g., UVM_ALL_ON | UVM_NOCOPY), or is there a practical use case where a positive flag by itself changes the behavior as expected?

I would appreciate any clarification on the design intent behind these flags.

[dave_59]

Field automation macros

Hi, Can anyone clear the following doubts? what is the default flag value set for a field, in field automation macros of an UVM class? I read that it is set to OVM_ALL_ON, if so why we need to explicitly set the same flag to the variable in the code? Is there any way to set the same flag for all the user defined fields in the derived class from an UVM base class? Or can we use regular expressions for the field name ? Thanks