Ilya Nedoluzhko wrote:
1) Why package definition is not supported? It is very useful because in
case of defined package I don't need to import some classes which are
physically located in this package. Moreover, in this case code to be
excuted will be absolutely legal to be exported into *.java file and
compiled using JDK, if it exists.
Hm. I don't quite get your point. All of
ExpressionEvaluator,
ScriptEvaluator and
ClassBodyEvaluator support a
setClassName() method, which allows you to define a custom class name and package.
SimpleCompiler and Compiler compile complete compilation units, where you can define your package and class name yourself.
So where is your problem?
2) While it is crucial to keep library size small - I agree, it is
necessary to support new Java 5 features, such as templates, foreach-style
cycles and autoboxing. Especially the last ones, because of importance in
scripting.
I added this as a feature request to JIRA, see
http://jira.codehaus.org/browse/JANINO-72
Please register on CODEHAUS JIRA and click "Watch it" on that page to monitor progress.
CU
Arno
