I’d say quite simply that I’d be willing to spend the money out of my salary for a DVT Eclipse IDE license in order to continue to use DVT. I can’t think of a better endorsement than that. The productivity benefits of using an IDE for code development are undeniable. Being able to sift through code quickly using the hyperlink functionality and the on-the-fly syntax checking that DVT provides has to reduce time spent compiling and debugging code by at least 50%, if not more.
I have been waiting for a tool like this since I learned to code in high school 20 years ago; It is about time. Think of the advances in technology since then and half the engineers are still using vi and grepping!
Without the DVT Eclipse IDE, trying to find the declaration for a task or function in third party IP in the context of an SOC is like finding a needle in a haystack. With DVT, it’s like a magnet, pulling the needle out of the haystack to quickly find what you are looking for. Without DVT, time is wasted identifying the source package of the function and it’s physical location in a directory on the file system. With DVT, you don’t even have to think about the location of the file or package containing the function. DVT does that for you.
The DVT Eclipse IDE has really enabled me to learn any new verification environment quickly by navigating easily through code. It’s also my primary editor, the auto-complete feature and the highlighting of syntax errors is a great feature and has saved me from doing multiple recompiles to get my syntax right. It is a powerful tool, helps one being more efficient and saves a lot of time!
The DVT Eclipse IDE has been extremely useful so far and I am using it heavily in my day-to-day development activity.
The DVT Eclipse IDE is my default tool of choice to navigate spaghetti code that I inherited from other people, or stitching up new piece of VIP into the test environment.
Personally I find the DVT Eclipse IDE indispensable for navigating around SystemVerilog classes and modules.
I switched to the good old gvim etc... but, after 30min, was really lacking the DVT Eclipse IDE, so I created a new cc view, remove the old one (to release my check outs) and could resume my activity. Just one or 2 hours lost. Nothing compared to the time the DVT Eclipse IDE saved me in these last 4 months...
I can’t say enough how much the DVT Eclipse IDE helped me speed up the learning curve. I tried my best to push out the tool but people were so used to using emacs and vi. Yet, whenever they see me doing debug and development with DVT, they were in awe.
The DVT Eclipse IDE has been fantastic throughout, and we are very happy with its capabilities, flexibility and support. I have been using the DVT Eclipse IDE for 5+ years and it continues to impress me with its features and ease of use.