# Maximal munch

In computer programming and computer science, "maximal munch" or "longest match" is the principle that when creating some construct, as much of the available input as possible should be consumed.

The earliest known use of this term is by R.G.G. Cattell in his PhD thesis[1] on automatic derivation of code generators for compilers.

## Application

For instance, the lexical syntax of many programming languages requires that tokens be built from the maximum possible number of characters from the input stream. This is done to resolve the problem of inherent ambiguity in commonly used regular expressions such as `[a-z]+` (one or more lower-case letters).[2]

The term is also used in compilers in the instruction selection stage to describe a method of "tiling" — determining how a structured tree representing a program in an intermediate language should be converted into linear machine code. An entire subtree might be converted into just one machine instruction, and the problem is how to split the tree into non-overlapping "tiles", each representing one machine instruction. An effective strategy is simply to make a tile of the largest subtree possible at any given point, which is called "maximal munch".[3]

## Drawbacks

In some situations, "maximal munch" leads to undesirable or unintuitive outcomes. For instance, in the C programming language, the statement `x=y/*z;` (without any whitespace) will probably lead to a syntax error since the `/*` character sequence (unintentionally) initiates a comment that is either unterminated or terminated by the end token `*/` of some later, unrelated actual comment (comments in C do not nest). What was actually meant in the statement was to assign to the variable `x` the result of dividing the value in `y` by the value obtained by dereferencing pointer `z`; this would be valid code. It can be stated by making use of whitespace or using `x=y/(*z);`.

Another example, in C++, uses the "angle bracket" characters `<` and `>` in the syntax for template specialization, but two consecutive `>` characters are interpreted as the right-shift operator `>>`.[4] Prior to C++11, the following code would produce a parse error, because the right-shift operator token is encountered instead of two right-angle-bracket tokens:

```    std::vector<std::vector<int>> my_mat_11; //Incorrect in C++03, correct in C++11.
std::vector<std::vector<int> > my_mat_03; //Correct in either C++03 or C++11.
```

The C++11 standard adopted in August 2011 amended the grammar so that a right-shift token is accepted as synonymous with a pair of right angle brackets (as in Java), which complicates the grammar but allows the continued use of the maximal munch principle. An exception to the maximal munch rule had to be added anyway to deal with the sequence `<::` which can appear in templates. In that case, unless the sequence is followed by `:` or `>` the character `<` is interpreted as its own token instead of part of the token `<:`.

## Alternatives

Programming languages researchers have also responded by replacing or supplementing the principle of maximal munch with other lexical disambiguation tactics. One approach is to utilize "follow restrictions", which instead of directly taking the longest match will put some restrictions on what characters can follow a valid match. For example, stipulating that strings matching `[a-z]+` cannot be followed by an alphabetic character achieves the same effect as maximal munch with that regular expression.[5] (In the context of regular expressions, the maximal munch principle is referred to as greediness and contrasted with laziness.) Another approach is to keep the principle of maximal munch but make it subordinate to some other principle, such as context (e.g., the right-shift token in Java would not be matched in the context of a generics expression, where it is syntactically invalid).[6]

## References

1. ^ Cattell, R. G. G. “Formalization and Automatic Derivation of Code Generators”. PhD thesis, 1978. Carnegie Mellon University, Pittsburgh, Pennsylvania, USA
2. ^ Aho et al., 168.
3. ^ Page, 470.
4. ^ Vandevoorde.
5. ^ Van den Brand et al., 26.
6. ^ Van Wyk et al., 63.

## Bibliography

• Aho, Alfred V.; Lam, Monica S.; Sethi, Ravi; Ullman, Jeffrey D. (2007). Compilers: Principles, Techniques & Tools (2nd ed.). Boston: Addison-Wesley. ISBN 978-0-321-48681-3.
• Page, Daniel (2009). "Compilers". Practical Introduction to Computer Architecture. Texts in Computer Science. London: Springer. pp. 451–493. doi:10.1007/978-1-84882-256-6_11. ISBN 978-1-84882-255-9.
• Van den Brand, Mark G.J.; Scheerder, Jeroen; Vinju, Jurgen J.; Visser, Eelco (2002). "Disambiguation Filters for Scannerless Generalized LR Parsers". Compiler Construction. Lecture Notes in Computer Science. Vol. 2304/2002. Berlin/Heidelberg: Springer. pp. 21–44. doi:10.1007/3-540-45937-5_12. ISBN 978-3-540-43369-9. ISSN 0302-9743.
• Vandevoorde, Daveed (14 January 2005). "Right Angle Brackets". Retrieved 31 March 2010.
• Van Wyk, Eric; Schwerdfeger, August (2007). "Context-aware scanning for parsing extensible languages". Proceedings of the 6th international conference on Generative programming and component engineering. New York: ACM. pp. 63–72. doi:10.1145/1289971.1289983. ISBN 9781595938558. S2CID 9145863.