* Generic support for compilers with built-in support for GCC/clang/VC++ * Display errors as code annotations or as tooltip in the editor window * Errors are clickable via the Build tab * codelite support the next generation debugger LLDB for OSX, Linux and Windows (remote debugging only for Windows) * Watches table - add persistent watches with a single click * Quick Watch - right click on a variable to expand it * Locals tree - automatically displays the current stack variables (also displays *this if available) * Threads view - contains a list of currently-running threads; switch between them with a single click * Breakpoint management - disable, enable, conditional, temporary * Automatic tree like tooltips * Memory view * Tree View tooltips (auto de-references pointers) * Allow modifying tooltips * Rename symbol * Rename file (will also change all #include in the code) * Rename local symbol * Generate setters / getters * Implement inherited virtual functions * Implement inherited pure-virtual functions * Easily change function signature to match its header / implementation counterpart * Move functions implementation to another source file * Implement all unimplemented methods

"*Code editor Like any other IDE, it includes a code editor that supports syntax highlighting and code completion using IntelliSense for variables, functions, methods, loops and LINQ queries. IntelliSense is supported for the included languages, as well as for XML and for Cascading Style Sheets and JavaScript when developing web sites and web applications. Autocomplete suggestions appear in a modeless list box over the code editor window, in proximity of the editing cursor. In Visual Studio 2008 onwards, it can be made temporarily semi-transparent to see the code obstructed by it. The code editor is used for all supported languages. *Debugger Visual Studio includes a debugger that works both as a source-level debugger and as a machine-level debugger. It works with both managed code as well as native code and can be used for debugging applications written in any language supported by Visual Studio. In addition, it can also attach to running processes and monitor and debug those processes. If source code for the running process is available, it displays the code as it is being run. If source code is not available, it can show the disassembly. The Visual Studio debugger can also create memory dumps as well as load them later for debugging. Multi-threaded programs are also supported. The debugger can be configured to be launched when an application running outside the Visual Studio environment crashes. *Windows Forms Designer The Windows Forms designer is used to build GUI applications using Windows Forms. Layout can be controlled by housing the controls inside other containers or locking them to the side of the form. Controls that display data (like textbox, list box, grid view, etc.) can be bound to data sources like databases or queries. Data-bound controls can be created by dragging items from the Data Sources window onto a design surface. The UI is linked with code using an event-driven programming model. The designer generates either C# or VB.NET code for the application. *WPF Designer The WPF designer, codenamed Cider, was introduced with Visual Studio 2008. Like the Windows Forms designer it supports the drag and drop metaphor. It is used to author user interfaces targeting Windows Presentation Foundation. It supports all WPF functionality including data binding and automatic layout management. It generates XAML code for the UI. The generated XAML file is compatible with Microsoft Expression Design, the designer-oriented product. The XAML code