C++ Compiler

⏱️ Why did my code stop running after 10 seconds?

All code executions have a 10-second timeout to prevent infinite loops and resource abuse. If you need longer execution, optimize your algorithm or break your task into smaller parts. This applies to compilation, execution, and terminal commands.

📦 How do I install external C++ libraries?

Click the Packages button to browse and install popular C++ libraries with one click. Available libraries include Boost, libcurl, jsoncpp, SQLite3, OpenSSL, SFML, SDL2, Qt5, and more. After installation, include headers in your code like #include <boost/algorithm/string.hpp>. Some libraries may require linking flags when compiling manually in the terminal.

💾 How does code saving and sharing work?

The IDE does NOT auto-save - you must click the Save button (Ctrl+S) to store your code in the database. After saving, click Share to get a permanent URL. Anyone with the link can view your code and click Fork to create their own editable copy. Each shared code tracks view counts and fork counts automatically.

🤝 Can I collaborate with others in real-time?

Real-time collaboration is not currently supported. However, you can share your code URL with others to view, and they can fork it to create their own copy. Work asynchronously by sharing updated links. Future updates may include live collaboration features.

🛠️ What C++ version and compiler are used?

The IDE uses GCC (GNU Compiler Collection) with C++17 standard by default. You can check the version by running g++ --version in the terminal. The platform is Linux x86_64 architecture. You can customize compilation flags in the terminal for different standards like C++20 using g++ -std=c++20 main.cpp -o program.

🐞 How does the GDB debugger work?

Click the Debug button to compile your code with the -g flag (debug symbols) and automatically run GDB. The debugger shows stack traces, backtraces, and variable values in the dedicated Debug tab. This is best for crash analysis and basic debugging. For advanced interactive debugging, use the terminal: gdb ./program.

⌨️ How do I provide input (stdin) to my program?

Use the Input tab in the right panel to type your program's stdin input, then click Run. Alternatively, in the terminal, save input to a file and use redirection: echo "test input" > input.txt then ./program < input.txt. The Input panel is the simplest method for interactive programs.

💻 What can I do in the integrated terminal?

The terminal supports file commands (ls, pwd, cat, mkdir), system info (uname, whoami), compiler tools (g++ --version, make --version), and manual compilation (g++ -O2 main.cpp -o program). Limitations: no interactive programs like vim/nano, and 10-second timeout per command. Perfect for custom build workflows and testing.

🗂️ Can I save multiple files or create projects?

Currently, the IDE supports single-file compilation only (main.cpp). Each save creates a new unique share ID. To create different versions, fork your own code or use different browser tabs with different share URLs. Multi-file project support with header files and separate compilation units is planned for future updates.

🚪 What happens to my code when I close the browser?

If you clicked Save, your code is permanently stored in the database and accessible via the share URL indefinitely. If you did NOT save, your code is lost when you close or refresh the page. Always click Save before closing to preserve your work. Share URLs are permanent and never expire.

🔒 Is my code private or public?

Unsaved code is only visible to you in your current session. Saved code is stored in the database but not publicly listed. Anyone with your share URL can view your code - treat share links as private and only share with intended recipients. Currently there is no authentication system, so links are the only access control.

⚠️ What if the IDE isn't working or I get errors?

For compilation errors, check the error messages in the Output tab and verify C++ syntax. For runtime crashes, use the Debug button to see stack traces. For timeout errors, optimize your code to run under 10 seconds. For package issues, verify installation via terminal: dpkg -l | grep <package>. If the IDE freezes, refresh your browser and avoid infinite loops in code.