[e-lang] Considering JSR 223 (scripting) implementation

[Kevin Reid]

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/>