update per current capability

improve and extend information on the POD config formats

Author: tbrowder

doc/Language/pod.pod6

@@ -46,16 +46,28 @@ different ways by different types of blocks, but is always specified using
 Perl6-ish option pairs. That is, any of:
 
 =begin table
- Value is...       Specify with...       Or with...       Or with...
- ===============   ===================   ==============   ==============
- Boolean (true)    :key                  :key(True)
- Boolean (false)   :!key                 :key(False)
- String            :key<str>             :key('str')      :key("str")
- Number            :key(23)              :key(4.6)
- List              :key[1, 'b', 3]       # not yet implemented
- Hash              :key{a=>1, b=>'x'}    # not yet implemented
+ Value is...       Specify with...           Or with...          Or with...
+ ===============   ===================       ==============      =========== 
+ List              :key[$e1,$e2,...]         :key($e1,$e2,...)
+ Hash              :key{$k1=>$v1,$k2=>$v2}
+ Boolean (true)    :key                      :key(True)
+ Boolean (false)   :!key                     :key(False)
+ String            :key<str>                 :key('str')         :key("str")
+ Number            :key(42)                  :key(2.3)
 =end table
 
+Where '$e1,$e2,...' are list elements of type Str, Int, Num, or
+Bool.  Lists may have mixed element types. Note that one-element
+lists are converted to the type of their element (Str, Int, Num, or
+Bool).
+
+For hashes, '$k1,$k2,...' are keys of type Str and '$v1,$2,...'
+are values of type Str, Int, Num, or Bool.
+
+Strings may use any of the single Q/q quote constructs, e.g.,
+:key(Q[str]), which is equivalent to the :key<str> format and
+results in an uninterpreted string literal.
+
 All option keys and values must, of course, be constants since Pod is a
 specification language, not a programming language. Specifically, option
 values cannot be closures. See Synopsis 2 for details of the various