CLion 2016.3 EAP, build 163.4396.13

Anastasia Kazakova

Last week we’ve started CLion 2016.3 EAP with user-defined literals support, CMake output window, C11 keywords completion and more. This week we bring a couple of important fixes to CLion 2016.3 EAP. Check the new EAP build 163.4396.13.

Doxygen support

Starting from v2016.2 CLion provides Doxygen support. This EAP adds support for \tparam tag, that means that CLion can now generate documentation stubs for template parameters in function, class or structure:
And if you rename the template parameter, Doxygen comment will be updated as well, so your documentation is always correct.

We’ve also fixed a problem with @return tag generated for constructors.

Code analysis

This build fixes several false positives in code analysis:

  • Local variable is never used for the variable used in sizeof().
  • Incorrect inspections when bitwise shift operators are used (CPP-7077).


There are also several debugger related fixes that bring more readable names for threads in the Frames toolwindow for LLDB, and allow displaying polymorphic variable when debugging.

Full release notes are available by the link.

Download the build and give it a spin. (Due to technical issues no patch-update from the previous build is available.) Your feedback is always welcome in our tracker and comments section below.

Download CLion 2016.3 EAP

Your CLion Team

The Drive to Develop

Comments below can no longer be edited.

5 Responses to CLion 2016.3 EAP, build 163.4396.13

  1. Sebastian says:

    September 20, 2016

    Hello Anastasia,

    After the fixes for C11 keywords I was wondering if you also plan to include fixes for GCC specific builtins such as this one:


    • Anastasia Kazakova says:

      September 20, 2016

      Thanks. We’ll check where in the queue we can put it.

  2. Maxim Tikhonov says:

    September 29, 2016

    You previously mentioned:
    >>Further plans
    >>Here are some things we had planned for CLion 2016.2 but which will only make it into the upcoming 2016.2.x updates. These are:
    >>Ability to watch command output during CMake execution.
    >>Several parsing problems which lead to red code in JUCE libraries (OC-8211).

    Did the fix for JUCE libraries ever made it to the 2016.2.x updates? I am on “2016.2.2 Build #CL-162.1967.7, built on September 5, 2016”, and the issues are still there.

    • Anastasia Kazakova says:

      September 30, 2016

      Unfortunately, this required more efforts that we’ve considered. So it’s still under development. We hope to have it done before 2016.3 release, but the changes are really big, so need more thinking and testing (not to break the performance significantly).

      • Maxim Tikhonov says:

        October 2, 2016

        Ok, thanks for info. Hopefully you will get it resolved some day 🙂


Subscribe for updates