SetupDesignGuide.pdf - Firmware Encoding Index
SetupDesignGuide.pdf - Firmware Encoding Index
SetupDesignGuide.pdf - Firmware Encoding Index
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Setup Design Guide<br />
DRAFT<br />
4<br />
VFR Programming Language<br />
4.1 BNF of VFR<br />
Character sequences that are in bold are key words. Keywords are case insensitive. The same<br />
extensions to BNF used to describe VFR are used here. Where elements are on separate lines in the<br />
BNF, those elements are required. VFR comments start with ‘//’ and end at the end of the line.<br />
The following ‘meta’-language elements are allowed on any line.<br />
::=<br />
::=<br />
::=<br />
define | define <br />
redefine | redefine <br />
include file-path<br />
Note: No comments are allowed on a file path line. The entire line from the first non-blank character<br />
following the include is taken as the file name.<br />
::=<br />
*<br />
endformset<br />
formset guid= title= nvstore=<br />
Note: is the current placeholder for the variable path.<br />
::=<br />
*<br />
endform<br />
form formid= title=<br />
::= | | | | | |<br />
| | | | | <br />
::=<br />
::=<br />
subtitle text=<br />
text text=<br />
::= varid= prompt= help=<br />
[location=,]<br />
, ::= <br />
Note: It is expected that the compiler will automatically allocate the location information in most cases.<br />
27