having recently heard about the imminent rease of version 1.0, I would like to present my view about the product, and pose a few questions. My findings stem from a mid-sized project on which I have been using CLion intensively and extensively for a couple of months now:
- I frequently see code passages which are marked red, and CLion presents some error message when hovering the mouse over them. However, the code compiles correctly, there really is no error
- on Linux (which is my favorite platform), the debugger often fails in the middle of stepping through the code. The buttons become grayed, and stepping is no longer possible. I also often see messages about some "timeout", and sometimes the loading of local variables takes extremely long.
- The fact that compile error messages are not parsed by CLion makes refactoring large code bases impractical. When I have, say 20 errors, and 80% of the console littered with compiler "proposals" and such, I move over to QtCreator, which gives me the error count and puts each error in one line, with related details available on request.
- MinGW on windows is unfortunately not up to date. Until recently I was able to work around that, but now I am depending on Xerces, and mingw isn't able to generate a usable Xerces build. BTW, mingw64 crashes when it sees boost precompiled headers.
In summary, I currently cannot rely on CLion as my sole IDE on any of my target platforms. It is always either the compiler or the debugger that fail at certain points. The fact that error messages aren't parsed is somtimes annoying, as are the wrong code error markers. There are, of course, a lot of points on the positive side, which, I would say, right now outweigh the problems. Remains the question whether these problems will get fixed, and if not, whether the commercial price point will tilt the balance towards the negative side. I hope you guys are holding some good stuff back to make moving to the for-pay version more appealing..
BTW, I would offer access to my project source code for tracking down the code analysis errors. I dont have time to isolate the issues to simple cases.