-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate a class hierarchy diagram for generated models #207
Comments
BTW, this information is in the Verilog DataModel itself, I find this documentation much better than any automatically generated diagram. Also, in the existing headers/*.h, the Object Factory is #if 0 #endif for the Abstract classes (You can't make an object). What form of annotation would you prefer if the above does not suffice? |
The documentation you are pointing to is a good read but not from a quick reference point of view right in the middle of programming session serving as a reference guide. I contend that there is a need for a supporting document. I find myself asking this question quite often - I need access to function I am still familiarizing myself with the source code. I am sure this pain will ease up with time as I memorize the hierarchy. But I would argue that anyone would have similar questions while onboarding. Here's a good example from Qt and Java My primary interest is the class hierarchy which will be immediately useful. The annotation calling out specific class whether or not it is abstract is a wish item. |
I once played aroud with generating dot files in #73 , but the graphviz rendering is not entirely useful and looks a bit messy due to the way each edge is rendered. |
Check out plantuml and elk layout. Python also has a few graph rendering engines that might be worth checking out. |
Title says it all. Annotating the class whether or not it is abstract will be helpful.
The text was updated successfully, but these errors were encountered: