What IDE is your choice for C/C++ project?

[bufalo1973]

KDevelop or QtCreator

[stephen hazel]

qtcreator now that i think windows10 is dieing and dieing fast.

[StarNamer work]

VSCode, but only because the only C/C++ I write is for the Arduino and similar microcontroller and Visual Studio doesn't support PlatformIO as far as I am aware.

[rjmoses]

For me, it's a toss-up between VSCode and Qt Creator. Have tried many others, like Codelite, and they all came up a little short. I've been using QT Creator longer, so I lean that way a little more.

[Gary R Wheeler]

You fancy-boys and your EDLIN. Real men, women, and those of blended gender use TECO[^].

Software Zen: delete this;

[Gary R Wheeler]

Huh. You actually need an entire farm of them? I edit my replacement microkernel for Windows 10 using a single paraplegic double-amputee lunar moth.

Software Zen: delete this;

[Gary R Wheeler]

I used Qt Creator 3-4 years back. The editing was pretty nice, but the build system had some holes in it. I had to do complete rebuilds every time I changed a resource, as the build didn't consider that significant :wtf: .

Software Zen: delete this;

[afigegoznaet]

Isn't the build system external to QtCreator?

[OldDBA]

There are some tasks for which I still use TECO.

[Gary R Wheeler]

It might have been. Like all open source tools, there's a certain amount of DIY associated with it. I would have expected, however, that it built it's own native projects correctly out-of-the-box. That was not the case when I used it.

Software Zen: delete this;

[Gary R Wheeler]

:omg: Are you running one of the versions for MS-DOS/Windows, or do you have an actual DEC machine?

Software Zen: delete this;

[afigegoznaet]

I guess you're talking about qmake. Well, there's a reason why they decided to move on to cmake.

[rkl_alx]

For me is Qt Creator, although Visual Studio 2017 is also quite good. I found that Qt Creator works very well with big projects. Visual Studio 2017 is also quite good, specially with the option of building remotely.

[OldDBA]

Now one of the dos/Windows versions. I first learned TECO on a PDP 10 in 1972 when my company moved from IBM to DEC. I used it professionally in TOPS-10, TOPS-20, RSX, and VMS. I now have Windows and Linux systems at home. If I could get a VMS system at a reasonable price I'd probably do so though more to get EVE/TPU than anything. Have been watching the group porting VMS to x86 with interest, but waiting to see what they offer to non-commercial users. Right now it looks like they offer a free limited-time license (alpha emulation) but you have to backup everything before it expires and re-download and re-install/restore. I'm not sure I want the hassle, though I loved working in that environment.

[Gary R Wheeler]

I did a fair amount of work on PDP-11's/RT-11 and Vaxen in the 1980's. My final project in that environment had a requirement that the delivered source code could only be in FORTRAN-77, which didn't support some of the VAX/VMS extensions I wanted to use. I wrote a code generator that converted the sources written for the extensions into pure 77. The generator was a combination of TECO macros and VAX/VMS DCL, and was probably one of the butt-ugliest things I've ever written.

Software Zen: delete this;