questions/suggestions

I have a couple of (mostly cosmetic) questions/suggestions:
1) is it possible to hide non-code files in project?
Currently I see VS solutions/projects and other files. While I think it's good to see
.c, .cc, .cpp, .h, .hpp, .inl, .txt (and maybe .mm and .m), so unless there already is some option to globally filter such files,
it would be nice to have (or at least an option to globally hide files not listed in CMakeLists)
2) a suggestion: how about add existing file(s), workaround is to put them in CMakeList manually, but it's a bit clumsy.

3) support for static analysis? (clang/cppcheck come to mind, probably as plugins? - I understand this is probably very low priority)
4) custom type visualizers for debugging (similar to natvis in VS), say I have custom made containers and I'd like them pretty-printed when debugging.
5) suggestion: hexadecimal numbers in watches when debugging (for ints - optionally)
3 comments
Comment actions Permalink

Thanks,

See some comments below:

1) is it possible to hide non-code files in project?
They are greyed out for now. But we are considering the way you suggest: https://youtrack.jetbrains.com/issue/CPP-505.

2) a suggestion: how about add existing file(s), workaround is to put them in CMakeList manually, but it's a bit clumsy.
This is in our plans as well: https://youtrack.jetbrains.com/issue/CPP-1749

3) support for static analysis? (clang/cppcheck come to mind, probably as plugins? - I understand this is probably very low priority)

We already have a static analysis running on the fly and even suggesting quick fixes for the problems. The list can be found and configured in Preferences/Settings | Editor | Inspections. There is a C/C++ group there. We also consider bundling clang analysis in the future: https://youtrack.jetbrains.com/issue/CPP-81


4) custom type visualizers for debugging (similar to natvis in VS), say I have custom made containers and I'd like them pretty-printed when debugging.

This can be done via gdbinit now (https://sourceware.org/gdb/onlinedocs/gdb/Writing-a-Pretty_002dPrinter.html). We set up the STL renders already following that way.


5) suggestion: hexadecimal numbers in watches when debugging (for ints - optionally)

Please, submit us a feature request here: https://youtrack.jetbrains.com/issues/CPP
0
Comment actions Permalink

Thanks Anastasia.
Sounds cool.
Regarding CLion inspector, I've noticed it has sometimes problems with my code :)
For example, it complains about *var (pointer type is required), but var is my smart pointer
with operators that convert to pointer type, i.e. operator const T *() const and operator T *().
I've also noticed it has problem with my delegates which have overloaded constructors with multiple values,
complaining about too many arguments.
I understand that parsing C++ is very difficult and I think this is not a big deal in terms of usability,
but I'm pretty sure CLion will improve in the future.

0
Comment actions Permalink

If you can suggest the false positives samples to our tracker, this could help us improve the code analysis in CLion. Thanks in advance.

0

Please sign in to leave a comment.