Source-code editor

Screenshot of using Notepad++ to edit XML code

A source-code editor is a text editor program designed specifically for editing source code of computer programs. It may be a standalone application or it may be built into an integrated development environment (IDE).

Characteristics

Source-code editors have characteristics specifically designed to simplify and speed up typing of source code, such as syntax highlighting, indentation, autocomplete and brace matching functionality. These editors also provide a convenient way to run a compiler, interpreter, debugger, or other program relevant for the software-development process. So, while many text editors like Notepad can be used to edit source code, if they do not enhance, automate or ease the editing of code, they are not source-code editors.

Structure editors are a different form of source-code editor, where instead of editing raw text, one manipulates the code's structure, generally the abstract syntax tree. In this case features such as syntax highlighting, validation, and code formatting are easily and efficiently implemented from the concrete syntax tree or abstract syntax tree, but editing is often more rigid than free-form text. Structure editors also require extensive support for each language, and thus are harder to extend to new languages than text editors, where basic support only requires supporting syntax highlighting or indentation. For this reason, strict structure editors are not popular for source code editing, though some IDEs provide similar functionality.

A source-code editor can check syntax while code is being entered and immediately warn of syntax problems. A few source-code editors compress source code, typically converting common keywords into single-byte tokens, removing unnecessary whitespace, and converting numbers to a binary form. Such tokenizing editors later uncompress the source code when viewing it, possibly prettyprinting it with consistent capitalization and spacing. A few source-code editors do both.^{[citation needed]}

The Language Server Protocol, first used in Microsoft's Visual Studio Code, allows for source code editors to implement an LSP client that can read syntax information about any language with a LSP server. This allows for source code editors to easily support more languages with syntax highlighting, refactoring, and reference finding.^[1] Many source code editors such as Neovim^[2] and Brackets^[3] have added a built-in LSP client while other editors such as Emacs,^[4] vim,^[5] and Sublime Text^[6] have support for an LSP Client via a separate plug-in.

History

The neutrality of this section is disputed. Please do not remove this message until conditions to do so are met. (June 2022) (Learn how and when to remove this template message)

This section needs expansion. You can help by adding to it. (June 2022)

In 1985, Mike Cowlishaw of IBM created LEXX while seconded to the Oxford University Press. LEXX used live parsing and used color and fonts for syntax highlighting. IBM's LPEX (Live Parsing Extensible Editor)^[7] was based on LEXX and ran on VM/CMS, OS/2, OS/400, Windows, and Java^[8]

Although the initial public release of vim was in 1991, the syntax highlighting feature was not introduced until version 5.0 in 1998.^{[9][better source needed]}

In 2003, Notepad++, a source code editor for Windows, was released by Don Ho. The intention was to create an alternative to the java-based source code editor, JEXT^[10]

In 2015, Microsoft released Visual Studio Code as a lightweight and cross-platform alternative to their Visual Studio IDE.^[11] In 2016, Visual Studio Code became the Microsoft product using the Language Server Protocol.^[1]

Comparison with IDEs

A source-code editor is one component of a Integrated Development Environment. In contrast to a standalone source-code editor, an IDE typically also includes debugger and build tools.

Standalone source code editors are preferred over IDEs by some developers when they believe the IDEs are bloated with features they do not need.^[12]

Notable examples

• Atom^[13]
• Brackets^[13]
• Eclipse
• Emacs
• Gedit
• NetBeans
• Notepad++^[13] (Windows only)
• SlickEdit
• Sublime Text^[13]
• TextMate (macOS only)
• UltraEdit^[13]
• vi/Vim
• Visual Studio Code^[13]

Controversy

Many source-code editors and IDEs have been involved in ongoing user arguments, sometimes referred to jovially as "holy wars" by the programming community.^{[14][better source needed]} Notable examples include vi vs. Emacs and Eclipse vs. NetBeans. These arguments have formed a significant part of internet culture and they often start whenever either editor is mentioned anywhere.

See also

• Integrated development environment
• Comparison of integrated development environments
• Comparison of online source code playgrounds
• Comparison of text editors § Programming features
• Comparison of JavaScript-based source code editors
• Comparison of hex editors
• Comparison of HTML editors
• List of text editors
• Editor war

References

0.00 (0 votes) Original source: https://en.wikipedia.org/wiki/Source-code editor. Read more