Talk:Interpreter pattern: Difference between revisions

Revision as of 15:14, 23 October 2013

Revision as of 15:15, 23 October 2013

Line 62:

A more general and useful definition might be a "Rules Engine" as [http://www.oodesign.com/interpreter-pattern.html OODesign.com] suggests. Really, it's a tree data structure of functional objects (each implementing the same single method). The functional objects "rules" delegate to one another until a terminal object (rule) is reached. The objects could be related through an interface and through the logic in their single implemented method instead of through an object-oriented inheritance hierarchy.

If no-one finds somewhere that this has already been stated clearly, I can add it to my blog and someone who doesn't know me can come along some day and use that as a source to improve this article.

--[[User:GlenPeterson|GlenPeterson]] ([[User talk:GlenPeterson|talk]]) 15:14, 23 October 2013 (UTC)