Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Interpreter pattern
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===What solution does the Interpreter design pattern describe?=== * Define a grammar for a simple language by defining an <code>Expression</code> class hierarchy and implementing an <code>interpret()</code> operation. * Represent a sentence in the language by an abstract syntax tree (AST) made up of <code>Expression</code> instances. * Interpret a sentence by calling <code>interpret()</code> on the AST. The expression objects are composed recursively into a composite/tree structure that is called ''abstract syntax tree'' (see [[Composite pattern]]). <br>The Interpreter pattern doesn't describe how to build an abstract syntax tree. This can be done either manually by a client or automatically by a [[parser]]. See also the UML class and object diagram below.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)