JonathanBromley Posted July 9, 2010 Report Share Posted July 9, 2010 1) The macro arguments are incorrectly documented. The first two arguments T, CB are swapped in the documentation - T shoudl be the type of the calling object, CB the type of the callback facade. The docs say "uvm_do_callbacks_exit_on(mycomp, mycb, ...)" 2) The macro is written as if it were a function body, which is fair enough because it must return a result. The documentation and examples, though, indicate wrongly that the macro itself should be called as if it were a function invocation. It's necessary to wrap it up in your own function. Anyone disagree? If not I'll log the bug early next week. cheers Quote Link to comment Share on other sites More sharing options...
JonathanBromley Posted July 9, 2010 Author Report Share Posted July 9, 2010 1) The docs say "uvm_do_callbacks_exit_on(mycomp, mycb, ...)" Ooops, sorry, they don't. If the doc said that it would be right. Instead it says "uvm_do_callbacks_exit_on(mycb, mycomp, ...)" which is wrong. In fact this error appears only in one specific place, the documentation of `uvm_do_callbacks_exit_on (the non-OBJ version). Unfortunately that's the one I used :-( Quote Link to comment Share on other sites More sharing options...
JonathanBromley Posted July 10, 2010 Author Report Share Posted July 10, 2010 Submitted Mantis item #3143. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.