Configuration file in the context of Computer data

In computer programming, a comment is text embedded in source code that a translator (compiler or interpreter) ignores. Generally, a comment is an annotation intended to make the code easier for a programmer to understand – often explaining an aspect that is not readily apparent in the program (non-comment) code. For this article, comment refers to the same concept in a programming language, markup language, configuration file and any similar context. Some development tools, other than a source code translator, do parse comments to provide capabilities such as API document generation, static analysis, and version control integration. The syntax of comments varies by programming language yet there are repeating patterns in the syntax among languages as well as similar aspects related to comment content.

The flexibility supported by comments allows for a wide degree of content style variability. To promote uniformity, style conventions are commonly part of a programming style guide. But, best practices are disputed and contradictory.

A computer language is a formal language for humans to communicate with a computer, not a natural language. In earlier days of computing (before the 1980s), the term was used interchangeably with programming language, but today, used primarily for taxonomy, is a broader term that encompasses languages that are not programming in nature. Sub-categories (with possibly contended hierarchical relationships) include:

• Construction
  • Programming – for controlling computer behavior
    • Command – for controlling the tasks of a computer, such as starting programs
    • Query – for querying databases and information systems
    • Transformation – for transforming the text of a formal language into text that meets a specific goal
  • Structural
    • Configuration – for writing configuration files
    • Data exchange – examples: JSON, XML
    • Markup – for annotating a document in a way that is syntactically distinguishable from the text, such as HTML
    • Page description – for describing the appearance of a printed page in a higher level than an actual output bitmap
    • Style sheet – for expressing the presentation of structured documents, such as CSS
• Modeling – for designing systems
  • Architecture description – for describing and representing system architecture
  • Hardware description – for modeling integrated circuits
• Simulation – for simulating
• Specification – for describing what a system should do