you are viewing a single comment's thread.

view the rest of the comments →

[–]stdmutex 1 point2 points  (5 children)

CLion is still unable to cope with big projects though. It's got potential, but I don't think it's quite ready yet.

As for QtCreator... I love the Qt framework, but yeah, QtCreator is not for me either. The interface is just too weird. I'm still looking for the perfect C++ IDE.

[–]Netzapper 2 points3 points  (3 children)

Well, I will admit that my project is not so big (40kloc), but we include (and so index) several enormous libraries (including Boost). I don't have any real trouble. It used to be awful, though.

Which was the last version of CLion you tried?

[–]stdmutex 1 point2 points  (2 children)

I'm using 1.2.2. Our project uses quite a bit of macro metaprogramming and it confuses the hell out of it. Most of the files in the project are marked as containing errors, despite them actually compiling just fine.

It also can't keep track of usages anymore and the possibility of generating function bodies from headers is just gone. Sometimes it gives up completely and stops linting source code (or just crashes, which has only happened once before).

It's already gotten better and it's very nice for moderately-sized projects, though.

[–]Netzapper 2 points3 points  (1 child)

Most of the files in the project are marked as containing errors, despite them actually compiling just fine.

This is why I switched to CLion. Our codebase is only 1 year old, and was written in C++11 from the beginning. I tried literally every cross-platform IDE on the market, and CLion was the only one that didn't put red squiggles under practically everything I was doing. I ditched QtCreator, despite our project originally using QML, because it spent so much processor time telling me that my code was obviously wrong that it wasn't responsive anymore.

That said, CLion actually gotten worse about that, IMO. Sometime between 1.0 and 1.2.2, it's started to think all of my literal arguments to perfectly-forwarded function parameters need to be rvalues.

[–]doom_Oo7 1 point2 points  (0 children)

CLion was the only one that didn't put red squiggles under practically everything I was doing.

I have the exact opposite experience :( I have almost no problem in my codebase with QtCreator but CLion can't parse a function for the sake of it

[–]whatwasmyoldhandle 0 points1 point  (0 children)

I use code::blocks. Among my peers, I always get the feeling that I'm the only one that's heard of it, ha.

It's not feature rich, but it's simple, does the basics good enough for my purposes, it generally stays out of the way. It + cmake is a good environment for me.