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
Template BLUEPHRASE HTML content elements Scripting visibility template [html · scripting] The template element is used to define HTML elements without making them visible to the visitor, setting them aside for future use.

Processing flow

The VLI operates on a rulebook, where a rulebook is the set of all V language source code files located in a common directory. The location of this directory is specified on the command line using the -d or --directory argument. The VLI runtime is invoked using the vv command.

console
$ vv -d /var/vermont/etc/conf.samples

A rulebook may optionally contain a VLI configuration file, which is itself written using the V language (albeit a restrictive subset). The configuration file specifies how the VLI trip-point evaluator should behave. By convention, the configuration file is called rulebook-options, but may be explicitly named using the -c or --config command line argument.

The runtime operates on each V language file that it finds in the rulebook directory (in no particular order), sending each file to the parser to start the process. The runtime may be instructed to operate on a portion of the rulebook, rather than the entire rulebook, by specifying a subset of files using the -f or --files command line argument.