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
Section BLUEPHRASE HTML writing composition Portion element section [html · structure] The section element is for authors to intentionally separate their writing into logical partitions.

Dependency tree

The dependency tree builder reorders the rulebook's base objects according to any dependencies specified in the source code files. By default, the ordering of objects is indeterminate, and will vary according to how the host's filesystem responds to a request to retrieve a glob of files. When one object must be evaluated before another object, the dependency keyword can be used to instruct the dependency tree builder to explicitly reorder the future use of those objects.

In this example, A is explicitly stated to be dependent upon B, so the order of evaluation will be altered such that B is evaluated before A. Note also that in this example, C is independent, and could be evaluated before, during, or after A and B.

sample-dependency.v
[A]
type = file
permissions = 640
path = /etc/sysconfig/network
dependency = B
        
[B]
type = file
permissions = 640
path = /etc/sysconfig/rsyslog
        
[C]
type = file
permissions = 640
path = /etc/sysconfig/i18n