{"id":8775,"date":"2016-08-11T23:32:59","date_gmt":"2016-08-11T22:32:59","guid":{"rendered":"https:\/\/sysprogs.com\/w\/?p=8775"},"modified":"2016-08-11T23:40:46","modified_gmt":"2016-08-11T22:40:46","slug":"clang-intellisense-improvements-in-visualgdb-5-2","status":"publish","type":"post","link":"https:\/\/sysprogs.com\/w\/clang-intellisense-improvements-in-visualgdb-5-2\/","title":{"rendered":"Clang IntelliSense improvements in VisualGDB 5.2"},"content":{"rendered":"

The upcoming VisualGDB 5.2\u00a0comes with several improvements to the\u00a0Clang IntelliSense engine that make the development experience easier and save time on common tasks. Let’s look at those in detail.\"include\"<\/a><\/p>\n

Performance<\/h2>\n

First of all, we have radically improved the IntelliSense performance. In VisualGDB 5.1\u00a0the bottleneck of the Clang IntelliSense engine was\u00a0computing\u00a0the\u00a0references to\u00a0variables and functions. For\u00a0source files with many included headers that could take\u00a05 seconds or more, putting\u00a0code completion and other features on hold. In VisualGDB 5.2 we have\u00a0eliminated this bottleneck by making code completion\u00a0and reference analysis\u00a0independent. No matter how huge your project\u00a0is and how long it takes to\u00a0reparse the source files, code\u00a0completion will\u00a0not be interrupted by it.<\/p>\n

Another\u00a0unnecessarily slow feature in VisualGDB 5.1 was the highlighting of nearby references to a\u00a0variable. If you were actively editing the source\u00a0code,\u00a0each\u00a0time you wanted to see the local references to a variable,\u00a0it took some annoying seconds for huge projects\u00a0because VisualGDB had to reparse the source file.\u00a0VisualGDB 5.2\u00a0goes smarter about this by immediately showing the references discovered earlier\u00a0and updating them once the last version of the file is reparsed.<\/p>\n

Automatic header file\u00a0discovery<\/h2>\n

Another\u00a0big\u00a0annoyance reported by our users was the need to manually\u00a0specify header search\u00a0paths\u00a0for imported\u00a0projects. While being straight-forward, it could easily take considerable time\u00a0and become annoying.\u00a0So in VisualGDB 5.2 we have decided to automate this. Each time\u00a0VisualGDB discovers\u00a0that some header files\u00a0are missing, it will automatically search the nearby directories for those files. If some files cannot be located, you will get a chance to pinpoint them manually or just tell VisualGDB to scan another directory recursively and locate them there:\"missing\"<\/a><\/p>\n

Once the directories have been located, you can add them to your project properties (and to IntelliSense properties) with on click of a mouse:\"addfiles\"<\/a><\/p>\n

If you are using\u00a0\u00a0GNU Make or CMake with VisualGDB-generated\u00a0make files, it will\u00a0insert the discovered directories there automatically,\u00a0saving you more time:\"debugmak\"<\/a><\/p>\n

Header inclusion stack<\/h2>\n

Another annoyance when working with\u00a0complex C++ projects\u00a0could be\u00a0understanding the context of an error in a header file.\u00a0Sometimes the code just before the #include<><\/strong> directive is responsible for the error, but finding it could be tricky if the file is included through a chain of other files.\u00a0In VisualGDB 5.2 we have added a\u00a0special popup that\u00a0shows the source file responsible for including the current\u00a0header file and allows navigating through the include chain with a few mouse clicks:\"stack\"<\/a><\/p>\n

Improved Find all References<\/h2>\n

We have also improved the Find Symbol Results\u00a0window. \u00a0In VisualGDB 5.2 it can\u00a0show variable assignments in a different color, distinguish references inside\u00a0preprocessor macros and it’s now based on the WPF technology, making it much more\u00a0responsive than the old window:\"refs\"<\/a><\/p>\n

Download<\/h2>\n

You can download\u00a0the preview version of VisualGDB 5.2 on the download page<\/a> and explore the new features yourself. If you have any feedback on it, you are more then welcome to share\u00a0it via our support form<\/a>\u00a0or\u00a0send us an email.<\/p>\n","protected":false},"excerpt":{"rendered":"

The upcoming VisualGDB 5.2\u00a0comes with several improvements to the\u00a0Clang IntelliSense engine that make the development experience easier and save time on common tasks. Let’s look at those in detail.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"categories":[1],"tags":[216],"_links":{"self":[{"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/posts\/8775"}],"collection":[{"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/comments?post=8775"}],"version-history":[{"count":11,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/posts\/8775\/revisions"}],"predecessor-version":[{"id":8793,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/posts\/8775\/revisions\/8793"}],"wp:attachment":[{"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/media?parent=8775"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/categories?post=8775"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sysprogs.com\/w\/wp-json\/wp\/v2\/tags?post=8775"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}