gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Use headings instead of bold text in index.md #238

Browse Source
This commit is contained in:
Jeroen Meulemeester
2016-01-03 21:14:30 +01:00
parent b6beffec2e
commit 3d642cdad7
66 changed files with 373 additions and 233 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
interpreter/index.md
View File

@ -10,19 +10,21 @@ tags:
- Difficulty-Intermediate
---
**Intent:** Given a language, define a representation for its grammar along
## Intent
Given a language, define a representation for its grammar along
with an interpreter that uses the representation to interpret sentences in the
language.
![alt text](./etc/interpreter_1.png "Interpreter")
**Applicability:** Use the Interpreter pattern when there is a language to
## Applicability
Use the Interpreter pattern when there is a language to
interpret, and you can represent statements in the language as abstract syntax
trees. The Interpreter pattern works best when
* the grammar is simple. For complex grammars, the class hierarchy for the grammar becomes large and unmanageable. Tools such as parser generators are a better alternative in such cases. They can interpret expressions without building abstract syntax trees, which can save space and possibly time
* efficiency is not a critical concern. The most efficient interpreters are usually not implemented by interpreting parse trees directly but by first translating them into another form. For example, regular expressions are often transformed into state machines. But even then, the translator can be implemented by the Interpreter pattern, so the pattern is still applicable
**Credits**
## Credits
* [Design Patterns: Elements of Reusable Object-Oriented Software](http://www.amazon.com/Design-Patterns-Elements-Reusable-Object-Oriented/dp/0201633612)