| 23 | | Due to the potential for changes in both input and output for {{{ippToPsps}}}, the code is heavily configurable. Configuration files are in an XML format, as this affords the most flexibility (human and machine readable, expandable, self-describing etc). {{{ippToPsps}}} is pointed to a config directory, under which subdirectories for each batch type hold the various XML config files. |
| | 23 | Due to the potential for changes in both input and output for {{{ippToPsps}}}, rather than hard-coding table descriptions, the code is heavily configurable. Configuration files are in an XML format, as this affords the most flexibility (human and machine readable, expandable, self-describing etc). {{{ippToPsps}}} is pointed to a config directory, under which subdirectories for each batch type hold the various XML config files. The skeleton for the files below are all created from the PSPS schema using the {{{pspsSchema2xml.pl}}} Perl script (found in the {{{ippToPsps/perl}}} directory). The same script also generates C header files for each batch-type. These headers contains enums for each PSPS table and are used by the code at runtime. This helps minimize code changes. |
