| |
|---|
| | of a configuration file, variable references (i.e., the values of |
|---|
| | variables) are always treated as |
|---|
| | .B strings. |
|---|
| | |
|---|
| | .IP \(bu 4 |
|---|
| | |
|---|
| | It is possible to load your own, user-defined, type in the variable |
|---|
| | descriptor object when you pre-define a symbol table to be passed to |
|---|
| | the parser. The problem is that this is more-or-less useless. The |
|---|
| | parser attempts to coerce data assignments in the configuration into |
|---|
| | the specified type. But, using only the assignment statements |
|---|
| | available in this language, you cannot define values in a meaningful |
|---|
| | way for user-defined types. So, assignment of user-defined variable |
|---|
| | types will always fail with a type error. Again, \*(TC is designed as |
|---|
| | a small configuration processing language, not as a general purpose |
|---|
| | programming language. In short, user-defined types are not supported |
|---|
| | in the variable descriptor processing and will always cause a type |
|---|
| | error to occur. |
|---|
| | |
|---|
| | |
|---|
| | .SH ADVANCED TOPICS FOR PROGRAMMERS |
|---|
| | |
|---|
| | Here are some ideas on how you might combine \*(TC features |
|---|
| |
|---|
| | |
tundra
authored
on 17 Jan 2005