Fix some typos and clarify some areas.

Fork: 0

tundra / tconfpy

Browse code Fix some typos and clarify some areas. master
1 parent 7041c98 commit 94092694229b62a31c4844c87ff7cad1b8633bb7 tundra authored on 29 Apr 2004

Patch

Unified Split

Showing 1 changed file

                Ignore Space
               Show notes
              View
            
          
          20 ■■■■■
          example.cfg
               # A 'tconfpy' Example Configuration File 
# Copyright 2003-2004 TundraWare Inc.
# $Id: example.cfg,v 1.102 2004/04/21 21:16:04 tundra Exp $
# $Id: example.cfg,v 1.103 2004/04/29 17:17:50 tundra Exp $
#
# This is designed to illustrate the various features
# of the 'tconfpy' configuration language.
#
 
.ifall $USER bar  # Both environment variable 'USER' and variable 'bar' must
                  # Exist for this to be true
 
   ifall = True   # Notice you cannot use variable 'IFALL' - it is predefines as Read Only
   ifall = True   # Notice you cannot use variable 'IFALL' - it is predefined as
                  # an internal variable for one of the reserved words
                  # and is marked as Read Only
 
.else             # If either or both did not exist - this is optional
 
    ifall = FALSE
 
# Logical NOR
 
.ifnone $USER bar # Neither environment variable 'USER' or variable
                  # 'bar' must exist for this to be true
                  # 'bar' may exist for this to be true
 
   ifnone = TRUE
 
.else
# Value Enforcement For Namespace Names
 
# You can make this fail if you supply 'test-tc.py' the 'limitns' option
 
[XYZ]                   # Error: Namespaces are limited to strings starting with 'NS'
[XYZ]                   # Error: the 'limitns' option requires namespaces to begin with 'NS'. 
                        # Notice that this is just a test driver feature to help you learn
                        # 'tconfpy'.  You can place any limits you like on namespace formation 
                        # in your own programs.
 
[]                      # But this always works because the root namespace is always legal
 
 
# Enforcing String Content
 # A 'tconfpy' Example Configuration File
 # Copyright 2003-2004 TundraWare Inc.
+# $Id: example.cfg,v 1.102 2004/04/21 21:16:04 tundra Exp $
+# $Id: example.cfg,v 1.103 2004/04/29 17:17:50 tundra Exp $
 #
 # This is designed to illustrate the various features
 # of the 'tconfpy' configuration language.
 #
 .ifall $USER bar  # Both environment variable 'USER' and variable 'bar' must
                   # Exist for this to be true
+   ifall = True   # Notice you cannot use variable 'IFALL' - it is predefines as Read Only
+   ifall = True   # Notice you cannot use variable 'IFALL' - it is predefined as
+                  # an internal variable for one of the reserved words
+                  # and is marked as Read Only
 .else             # If either or both did not exist - this is optional
     ifall = FALSE
 # Logical NOR
 .ifnone $USER bar # Neither environment variable 'USER' or variable
+                  # 'bar' must exist for this to be true
+                  # 'bar' may exist for this to be true
    ifnone = TRUE
 .else
 # Value Enforcement For Namespace Names
 # You can make this fail if you supply 'test-tc.py' the 'limitns' option
+[XYZ]                   # Error: Namespaces are limited to strings starting with 'NS'
+[XYZ]                   # Error: the 'limitns' option requires namespaces to begin with 'NS'.
+                        # Notice that this is just a test driver feature to help you learn
+                        # 'tconfpy'.  You can place any limits you like on namespace formation
+                        # in your own programs.
 []                      # But this always works because the root namespace is always legal
 # Enforcing String Content

Show line notes below