Jump to content

the invocation order of do_copy and __m_uvm_field_automation in uvm_object::copy

Recommended Posts


Any idea that in the uvm_object::copy implementation the do_copy is prior to the __m_uvm_field_automation while in the others, like print, compare, pack and unpack the do_* function calls are following the __m_uvm_field_automation calls?

In my opinion putting the do_* after the __m_uvm_field_automation is better than the reversed order of the placement since it gives the derivation of uvm_object all the rights to deal with any kind of exceptions. It also keeps the consistency between the field automation method and do_* methods.



Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...