Intel XENIX 286 Programmers Guide (86) - Tenox.tc

Intel XENIX 286 Programmers Guide (86) - Tenox.tc Intel XENIX 286 Programmers Guide (86) - Tenox.tc

09.06.2013 Views

XENIX Programming lex: Lexical Analyzer Generator Or you might want to treat this as = -a. To do this, just return the minus sign as well as the letter to the input. The following performs the interpretation: = -[a-zA-Z] { printf(" Operator ( = -) ambiguous\n"); yyl ess(yyl eng-2); action for = } Note that the expressions for the two cases might more easily be written = -/[A-Za-z] in the first case and = /-[A-Za-z] in the second: no backup would be required in the rule action. It is not necessary to recognize the whole identifier to observe the ambiguity. The possibility of =-3 however, makes =-![" \t\n] a still better rule. In addition to these routines, lex also permits access to the 1/0 routines it uses. They include • input returns the next input character. • output(c) writes the character c on the output. • unput(c) pushes the character c back onto the input stream to be read later by input. By default these routines are provided as macro definitions, but the user can override them and supply private versions. These routines define the relationship between external files and internal characters and must all be retained or modified consistently. They may be redefined, to cause input or output to be transmitted to or from strange places, including other programs or internal memory; but the character set used must be consistent in all routines; a value of zero returned by input must mean end-of-file; and the relationship between unput and input must be retained or the look-ahead will not work. lex does not look ahead at all if it does not have to, but every rule containing a slash (/) or ending in one of the following characters implies look-ahead: + * ? $ Look-ahead is also necessary to match an expression that is a prefix of another expression. The standard lex library imposes a 100-character limit on backup. 9-11

lex: Lexical Analyzer Generator XENIX Programming Another lex library routine that you sometimes want to redefine is yywrap, which is called whenever lex reaches an end-of-file. If yywrap returns a 1, lex continues with the normal wrapup on end of input. Sometimes, however, it is convenient to arrange for more input to arrive from a new source. In this case, the user should provide a yywrap that arranges for new input and returns 0. This instructs lex to continue processing. The default yywrap always returns 1. This routine is also a convenient place to print tables, sum maries, etc. at the end of a program. Note that you cannot write a normal rule that recognizes end-of-file; the only access to this condition is through yywrap. In fact, unless a private version of input is supplied, a file containing nulls cannot be handled, since a value of 0 returned by input is taken to be end-of-file. Hand ling Ambiguous Sou rce Rules lex can handle ambiguous specifications. When more than one expression can match the current input, lex chooses as follows: • The longest match is preferred. • Among rules that match the same number of characters, the first given rule is preferred. For example, suppose the following rules are given: integer [a-z] + keyword action ... ; identifier action . .. ; If the input is integers, it is taken as an identifier, because [a-z] + matches eight characters while integer matches only seven. If the input is integer, both rules match seven characters, and the keyword rule is selected because it was given first. Anything shorter (e.g., int) does not match the expression integer, so the identifier interpretation is used. The principle of preferring the longest match makes certain constructions dangerous, such as the following: 9-12 *

lex: Lexical Analyzer Generator <strong>XENIX</strong> Programming<br />

Another lex library routine that you sometimes want to redefine is yywrap, which is<br />

called whenever lex reaches an end-of-file. If yywrap returns a 1, lex continues with<br />

the normal wrapup on end of input. Sometimes, however, it is convenient to arrange for<br />

more input to arrive from a new source. In this case, the user should provide a yywrap<br />

that arranges for new input and returns 0. This instructs lex to continue processing.<br />

The default yywrap always returns 1.<br />

This routine is also a convenient place to print tables, sum maries, e<strong>tc</strong>. at the end of a<br />

program. Note that you cannot write a normal rule that recognizes end-of-file; the only<br />

access to this condition is through yywrap. In fact, unless a private version of input is<br />

supplied, a file containing nulls cannot be handled, since a value of 0 returned by input is<br />

taken to be end-of-file.<br />

Hand ling Ambiguous Sou rce Rules<br />

lex can handle ambiguous specifications. When more than one expression can ma<strong>tc</strong>h the<br />

current input, lex chooses as follows:<br />

• The longest ma<strong>tc</strong>h is preferred.<br />

• Among rules that ma<strong>tc</strong>h the same number of characters, the first given rule is<br />

preferred.<br />

For example, suppose the following rules are given:<br />

integer<br />

[a-z] +<br />

keyword action ... ;<br />

identifier action . .. ;<br />

If the input is integers, it is taken as an identifier, because<br />

[a-z] +<br />

ma<strong>tc</strong>hes eight characters while<br />

integer<br />

ma<strong>tc</strong>hes only seven. If the input is integer, both rules ma<strong>tc</strong>h seven characters, and the<br />

keyword rule is selected because it was given first. Anything shorter (e.g., int) does not<br />

ma<strong>tc</strong>h the expression integer, so the identifier interpretation is used.<br />

The principle of preferring the longest ma<strong>tc</strong>h makes certain constructions dangerous,<br />

such as the following:<br />

9-12<br />

*

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!