The MIF uses either the International Standards Organization document ISO 8859-1 (Latin Alphabet No. 1) or the Unicode 1.1 Specification for its character sets. If a Unicode MIF is provided, the first octet of the .MIF file must be 0xFE (hexadecimal) and the second must be 0xFF. Otherwise, the Service Layer treats the file as an ISO8859-1 MIF.
There are four classes of tokens: keywords, integer constants, strings (literals), and separators. Two keywords, “start” and “end,” are scope keywords, which are only useful when followed by another keyword. Blanks, tabs, new lines, carriage returns, and comments (collectively known as "white space") as described following are ignored except when they serve as separate tokens. White space is required to separate adjacent keywords and constants.
MIF is case-insensitive in all situations, except for literal strings where characters surrounded by double quotes are case-sensitive.
Literal strings separated by white space are concatenated and stored as one literal string.
|
Copyright © 2013 CA.
All rights reserved.
|
|