CLion 2017.3 EAP: CMake 3.9 and new color scheme settings

Anastasia Kazakova

Hi,

A new CLion 2017.3 EAP (build 173.2941.5) is now available!

Download CLion 2017.3 EAP

Color scheme for C/C++

C/C++ color settings now allow to distinguish function calls and function declarations (CPP-4519). Previously you can only do that through the Editor -> Color Scheme -> Language Defaults, that are common for all languages supported by CLion. Now separate settings for C/C++ are available:
function_call_declaration

For example, you can make function declarations bold and keep function calls in regular font:
colors_sample

This build also bundles CMake 3.9. The full list of changes is available by the link.

Previous CLion 2017.3 EAP builds addressed:

Download CLion 2017.3 EAP

Your CLion Team
The Drive to Develop

Comments below can no longer be edited.

8 Responses to CLion 2017.3 EAP: CMake 3.9 and new color scheme settings

  1. Anton says:

    October 5, 2017

    Please, consider adding a different highlighting for built-in types. They aren’t just C++ keywords. They are types: bool, int, short, long, float, etc. I created an issue for this in 2014: https://youtrack.jetbrains.com/issue/CPP-880

    • Anastasia Kazakova says:

      October 6, 2017

      Thanks, we’ll consider.

  2. Olof says:

    October 6, 2017

    I’m not seeing much about performance and C++ correctness in these last few EAP’s.

    I know there are initiatives in progress. Could we get an update?

    • Anastasia Kazakova says:

      October 9, 2017

      You are right, at the moment there are several tasks in progress (mostly correctness, but some performance changes are in progress as well). We’ll share an update when they are ready and published in the EAP build.

      • Roman says:

        October 9, 2017

        My subjective feelings is that most of performance problems lie in how caching and incremental changes are handled. When Clion is “warmed-up” it works pretty fast even on large projects.
        But huge freezes can happen if:
        1) I close project and reopen it again.
        2) I add new .cpp to CMakeLists.txt and then “reload” project

        Second issue turned out to be too painful for me, so switched to other IDE. I just don’t understand why I should wait 3 minutes after adding new empty file to project. You should detected a diff in project model and re-parse only new added file.

        • Anastasia Kazakova says:

          October 10, 2017

          Thanks you for your feedback and sorry for such an experience.

          CLion usually tries to detect changes and reparse incrementally only necessary things (at least, when C++ allows it). However, CLion calls CMake on any CMake files changes to apply these changes, this could cause issues and degradations. We’ll see if we can possibly improve the performance in that case. Thank you again for sharing this with us!

        • Anastasia Kazakova says:

          October 10, 2017

          Could you please provide a CPU snapshot for case 2) for us to investigate the issue: https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems

Subscribe

Subscribe for updates