CSC/ECE 517 Summer 2008/wiki1 7 ev: Difference between revisions
(→Links) |
|||
Line 143: | Line 143: | ||
[http://www.beanshell.org/manual/bshmanual.html#Calling_BeanShell_From_Java Calling BeanShell from Java] | [http://www.beanshell.org/manual/bshmanual.html#Calling_BeanShell_From_Java Calling BeanShell from Java] | ||
[http://www.jdocs.com/beanshell/2.0.b4/api-index.html?m=class&p=bsh&c=Interpreter&render=classic link name] | |||
[http://www.google.com/search?hl=en&q=ExpressionEvaluator.parseExpression+dynamic link name] | |||
[http://forum.java.sun.com/thread.jspa?threadID=474563&tstart=75 link name] | |||
[http://forum.java.sun.com/thread.jspa?threadID=5132451&messageID=9524869 link name] | |||
[http://www.ibm.com/developerworks/java/library/j-javascripting1/ link name] | |||
[http://java.sun.com/j2ee/1.4/docs/api/javax/servlet/jsp/el/Expression.html link name] | |||
[http://www.developintelligence.com/javadoc/javax/servlet/jsp/el/ExpressionEvaluator.html#evaluate(java.lang.String,%20java.lang.Class,%20javax.servlet.jsp.el.VariableResolver,%20javax.servlet.jsp.el.FunctionMapper) link name] | |||
[http://www.beanshell.org/manual/embeddedmode.html#eval() link name] | |||
[http://www.beanshell.org/manual/embeddedmode.html link name] |
Revision as of 01:20, 2 June 2008
Introduction
- A
Pros and cons
As with any feature there is a price to pay for the benefits.
Pros
- Dynamic Metaprogramming Capability
- Flexibilility
- Ease of Use
Cons
- Performance
- Security
Ruby Example
The eval function can be used for dynamically calling functions. For example in Ruby:
# Create an array of functions functions = ['function1','function2','function3'] # Define functions def function1() puts "inside function1" end def function2() puts "inside function2" end def function3() puts "inside function3" end # Factory Pattern def CallFunction(functionname) eval functionname end #Results irb(main):039:0> CallFunction functions[0] inside function1 => nil irb(main):040:0> CallFunction functions[1] inside function2 => nil irb(main):041:0> CallFunction functions[2] inside function3 => nil
What makes this so powerful is that the function names in the array can be stored in an array or someplace else like a database or xml file.
Taking this one step further we can store the function definition in an array as well:
#Create an array for the function name and function definition function1 = ['function4'] # We could have more then one function2 =['def function4 () puts "inside function4" end'] # We could have more then one # Dynamically create/define function eval function2[0] # Dynamically call the the name of the function irb(main):060:0> eval function1[0] inside function4 => nil
So, in this example function4() is created dynamically at run-time. This allows us to store parts of the code as data and to create functions when needed. An application written using eval to dynamically generate functions would allow new functions to be added easily. For example, you could create new definitions of functions and insert them into a database table.
Java Example
The base Java language does not have a direct equivalent to Ruby's eval() facility, because Java is a compiled, statically typed language. However, Java environments can use a facility similar to Ruby's eval() through the BeanShell addon, available from http://beanshell.org/bsh-2.0b4.jar. Because a Java program can create instances of the BeanShell interpreter, and submit arbitrary Java code to the interpreter for evaluation at run time, Java developers can take advantage of BeanShell's eval facility to create programs that create and execute new programs on the fly. BeanShell retains state across invocations, so that previously evaluated methods and variables are available to methods and variables that are evaluated later in the lifetime of each BeanShell instance.
BeanShell is distributed as an executable jar, which when run, provides a BeanShell workspace in which Java code can be developed in a command line environment. To view the output from the code below in the BeanShell Workspace, the user must invoke "File->Capture System in/out/err" from the "Bsh Workspace" menu, before running the code.
import java.lang.StringBuffer; // needed for mutable strings // Create an array for function names StringBuffer[] functions = new StringBuffer[4]; // Define functions void function1() {System.out.println("inside function1");} void function2() {System.out.println("inside function2");} void function3() {System.out.println("inside function3");} // Factory Pattern void CallFunction (functionname) {eval(functionname + "();");} // Initialize function names functions[0] = new StringBuffer("function1"); functions[1] = new StringBuffer("function2"); functions[2] = new StringBuffer("function3"); // Results bsh % CallFunction (functions[0]); inside function1 bsh % CallFunction (functions[1]); inside function2 bsh % CallFunction (functions[2]); inside function3 bsh %
As in the Ruby example, the function names in the array can be stored in an array, or someplace else like a database or xml file.
In addition, similar to the Ruby example, we can store the function definition in an array as well:
// Create an array for the function name and function definition StringBuffer[] function1 = new StringBuffer[10]; StringBuffer[] function2 = new StringBuffer[10]; // Dynamically create/define function function1[0] = new StringBuffer("function4"); // Dynamically call the the name of the function bsh % function2[0] = new StringBuffer("void function4() {System.out.println(\"inside function 4\");}"); bsh % eval(function2[0].toString()); bsh % CallFunction (function1[0]); inside function 4 bsh %
As in the Ruby example, in this Java example using BeanShell eval(), function4() is created dynamically at run-time. This allows us to store parts of the code as data and to create functions when needed. An application written using eval to dynamically generate functions would allow new functions to be added easily. For example, you could create new definitions of functions and insert them into a database table.