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

Work towards #56: Add permalink to every pattern

Browse Source 
This makes cleaner URLs thanks to jekyll
This commit is contained in:
Markus
2015-08-15 18:03:05 +02:00
parent fbb12b53ba
commit fdb9be1e76
57 changed files with 113 additions and 80 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
interpreter/index.md
View File

@ -2,6 +2,7 @@
layout: pattern
title: Interpreter
folder: interpreter
permalink: /patterns/interpreter/
categories: pattern_cat
tags: pattern_tag
---
@ -16,4 +17,4 @@ language.
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
* 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