C and C++ Compiler

Most people learning C or C++ do not need a development environment the size of a small operating system. They need somewhere to type a program, a key that compiles and runs it, and an honest account of what went wrong.

This is that. It opens a file, colors it properly, compiles it with a keypress and shows you what the program printed — in one window, with nothing to set up.

Clang 23 and a complete Windows runtime ship inside the app. On a PC that has never seen a compiler, your first program builds immediately: no MinGW download, no PATH, no installer, no version to choose. Every program is built standalone, so the .exe it leaves beside your source runs on any other PC too.

Syntax color, folding, bracket matching and completion that knows the C and C++ keywords, the standard functions and the headers you are most likely to reach for. A tab per file, each with its own undo. Shift+Alt+F tidies the whole file with clang-format.

.c files compile as C17 and .cpp files as C++20. Settings goes back to C89 or forward to C23 and C++23, adds optimization, or takes any compiler flags you like.

F5 compiles and runs. Output arrives in the panel as it is printed, and when your program asks for input with scanf or cin you answer it right there. Ctrl+F5 feeds it input.txt from the same folder instead, the way contest problems are practiced.

Open a folder and the files beside yours are compiled in with it, so a main.cpp that calls into utils.cpp just works. Files with a main of their own are left out, so a folder of separate exercises still builds one at a time.

A great deal of C and C++ is still taught from Turbo C. Here conio.h works — clrscr(), gotoxy(), textcolor(), textbackground(), getch() and kbhit() — along with dos.h's delay() and the old iostream.h. Programs that draw on the console get a real console window of their own, found automatically, which stays open at the end so you can read the last line.

A compiler error becomes a line you can click, with the same error in a sentence underneath: why cout is undeclared, what a missing semicolon looks like from the compiler's side, why main has to return int. Warnings show up even when the program builds, because an unused variable or a mismatched printf is where the real lessons are.

If the program crashes, you are told how: an access violation from a bad pointer, a stack overflow from endless recursion, a division by zero — not just a negative number.

The assistant panel can see the file you are on. Select some lines and it sees those too; build something that fails and the errors go with your question.

No AI service is included with this app, and none is being sold to you here. The assistant is inert until you enter an API key of your own, and the price of this app buys the editor and the compiler — not the model behind that key. Whatever you spend asking questions is billed to you by the provider you chose, on your own account, and never passes through us.

Bring a key from Claude, ChatGPT, Gemini or OpenRouter, or point it at Ollama or LM Studio on this PC and it works offline. The key is kept on this PC, outside the settings file.

Sixteen snippets, eight in C and eight in C++: reading input safely, pointers, malloc and free, files, strings, vectors, sorting, maps, classes, timing and random numbers. Each opens in its own tab as a complete program you can run before you change a line.

It is an editor and a compiler, not a full development environment. There is no debugger and no breakpoints. It cannot compile with Microsoft's own compiler, and Turbo C's graphics.h has no equivalent here.

No account. No sign-in. No ads. The app makes no network call of its own; the only thing that ever leaves your PC is a question you type into the assistant, going to the provider whose key you entered, or feedback you choose to send.

Built for Windows 11, and at home on Windows 10.