| | BUG FIXES |
|---|
| | |
|---|
| | - There was a problem properly identifying templates |
|---|
| | if they were named using fully qualified names that |
|---|
| | included one or more namespaces. Fixed. |
|---|
| | - There was a problem properly identifying templates if they were |
|---|
| | named using fully qualified names that included one or more |
|---|
| | namespaces. Fixed. |
|---|
| | |
|---|
| | CHANGES |
|---|
| | |
|---|
| | |
|---|
| | - More and better validation is done of parameters passed to |
|---|
| | the parsing API: |
|---|
| | |
|---|
| | In addition to the initial symbol table, the passed |
|---|
| | template table is also checked. |
|---|
| | In addition to the initial symbol table, the passed template table |
|---|
| | is also checked. |
|---|
| | |
|---|
| | The initial value for each passed symbol is checked for |
|---|
| | valid type in both the symbol table and the template table passed |
|---|
| | to the API. |
|---|
| | The initial value for each passed symbol is checked for valid type |
|---|
| | in both the symbol table and the template table passed to the API. |
|---|
| | |
|---|
| | Template names are checked to make sure they do not contain |
|---|
| | namespace separators. Templates must be named canonically. |
|---|
| | This was previously the case, but not checked. |
|---|
| | Template names are checked to make sure they do not contain |
|---|
| | namespace separators. Templates must be named canonically. This |
|---|
| | was always a requirement, but it was never checked or documented. |
|---|
| | |
|---|
| | - The program changes described below have made the 'ParseConfig' |
|---|
| | API incompatible with previous versions of 'tconfpy'. The version |
|---|
| | number has been branched to 2.x to reflect this fact. Existing |
|---|
| |
|---|
| | |
tundra
authored
on 19 Jan 2005