|
Considering JSR 223 (scripting) implementation
|
View:
New views
2 Messages
—
Rating Filter:
Alert me
|
 |
Considering JSR 223 (scripting) implementation
by Kevin Reid-2
::
Rate this Message:
MarkM: Could you ask a handy Java programmer (possibly mikesamuel) or
two these questions? * Is JSR 223 something which ought to be supported by a JVM-based language; is it an expected feature? If not, is it otherwise *worth* implementing? * Is there an existing application which uses the JSR 223 interfaces in nontrivial ways and would therefore be useful as a testing tool? * The JSR 223 specification and test suite (TCK) are hidden behind various licenses or other restrictions. In general, what are the implications of this for an open source, non-formally-organized project? * The JSR 223 specification is hidden behind license agreements which distinguish between writing an “application” and an “implementation” of the specification. Is 1. an “implementation” an implementation of the classes in the javax.script package, i.e. ScriptEngineManager and so on, and an “application” code which uses those classes/interfaces in any way, 2. an “implementation” classes which implement the interfaces so as to be a JSR-223 scripting language, and an “application” code which uses those interfaces to use scripting languages as plugins, or 3. something else? -- Kevin Reid <http://switchb.org/kpreid/> _______________________________________________ e-lang mailing list e-lang@... http://www.eros-os.org/mailman/listinfo/e-lang |
|
|
Re: Considering JSR 223 (scripting) implementation
by Ben Laurie-3
::
Rate this Message:
On Sat, Oct 24, 2009 at 4:01 AM, Kevin Reid <kpreid@...> wrote:
> MarkM: Could you ask a handy Java programmer (possibly mikesamuel) or > two these questions? > > * Is JSR 223 something which ought to be supported by a JVM-based > language; is it an expected feature? If not, is it otherwise > *worth* > implementing? > > * Is there an existing application which uses the JSR 223 interfaces > in nontrivial ways and would therefore be useful as a testing tool? > > * The JSR 223 specification and test suite (TCK) are hidden behind > various licenses or other restrictions. In general, what are the > implications of this for an open source, non-formally-organized > project? Sun sponsors open source by making TCKs available free of charge to them. > * The JSR 223 specification is hidden behind license agreements which > distinguish between writing an “application” and an > “implementation” > of the specification. Is > > 1. an “implementation” an implementation of the classes in the > javax.script package, i.e. ScriptEngineManager and so on, and an > “application” code which uses those classes/interfaces in any > way, > > 2. an “implementation” classes which implement the interfaces so as > to be a JSR-223 scripting language, and an “application” code > which uses those interfaces to use scripting languages as > plugins, or > > 3. something else? > > > -- > Kevin Reid <http://switchb.org/kpreid/> > > > > > _______________________________________________ > e-lang mailing list > e-lang@... > http://www.eros-os.org/mailman/listinfo/e-lang > e-lang mailing list e-lang@... http://www.eros-os.org/mailman/listinfo/e-lang |
| Free embeddable forum powered by Nabble | Forum Help |
