No side effects, no surprises.

  1. Welcome
    1. What is the V language?
    2. What problem does this solve?
    3. “Working knowledge” is a critical dependency
    4. System documentation through executable rulebooks
    5. Usage scenarios
  2. Traits
    1. No side effects
    2. Declarative statements
    3. Objects
    4. Syntactic rules
    5. Sample
  3. Interpreter
    1. Language vs. Interpreter
    2. Rulebooks
    3. VLI Architecture
    4. Processing flow
    5. Object scope
    6. Object composer
    7. Dependency tree
    8. Resource evaluator
    9. Variable substitution
    10. Rule validator
    11. Trip-point emitter
  4. Installation
    1. Prerequisites
    2. Download
    3. Setup
Build-notes BLUEPHRASE Pragma endnotes footnotes Section back-matter build-notes [bluephrase · pragmas] The "build-notes" pragma is used to instruct the BLUE PROCESSOR to build an Endnotes or Footnotes back-matter section from manuscript notemarks.

What problem does this solve?

The problem domain addressed by V is computer administration.

V provides a syntax and grammar for monitoring and reporting: it is well suited to monitor software configurations, application performance, and system vulnerabilities.

In practice, V is used in a manner similar to some scripting languages (like Bash and Perl), to solve problems with a well-defined set of inputs. It is not used as an application development language, and it is not typically well suited to solving problems with arbitrary user inputs.