Reto, all
Currently I did not spent any time on 2.8. There shouldn't be any show
stoppers to get the scripting engine to work with Scala 2.8 however.
A bit more critical is SLING-1255 (caching of pre compiled scripts)
however. Without this being fixed usability is a bit limited.
I think the scripting engine should ultimately end up in a place which
is closer to either the Scala community or the JSR 223 community. At
Scala Days the Scala team (re-)announced [2] code repositories for 3rd
party contributions. I think it might be worthwhile to check whether we
could move the Scala scripting engine to the Scala incubator [3]. This
would make it much easier for non Sling committers (like me and Reto I
suppose) to get things done and to use the script engine. Furthermore
the scripting engine would ultimately profit from contributions from
users of different backgrounds.
WDYT?
Michael
[1] https://issues.apache.org/jira/browse/SLING-1255
[2]
http://scala-programming-language.1934581.n4.nabble.com/From-incubator-to-greenhouse-to-trunk-td2009739.html
[3] http://github.com/scala-incubator
On 4/26/10 10:57 AM, Reto Bachmann-Gmuer wrote:
Hi Michael
I saw you notes for Scala Days 2010, cool to see there's JSR 223
support. I was looking at the scala moduke again to see what needs to
be updated for using scala 2.8.
I would like to see one jsr 223 compliant scala bundle that has no
clerezza or sling dependency and can be used in both projects. How
close is the sling bundle to this? Is there already some 2.8 code
around? what's the best location for such a common bundle? I happily
use a sling bundle (as long as it has no sling dependencies), but I
wouldn't mind being able to contribute :)
Cheers,
reto
On Fri, Dec 11, 2009 at 10:27 PM, Michael Dürig<michael.due...@day.com> wrote:
- The variable bindings mechanism needs to be improved. I see there is
some
effort in clerezza regarding this.
It's very raw at the moment but it should be possible to have an object
appearing to be of all the visible types on the scala side.
I attached a patch to SLING-1236 [1] which implements this. I.e. values
passed to the script appear to be of all visible types. I achieve this by
using implicit conversion:
For a value v of type T let S be the smallest super type of T which is
accessible. Then v is exposed with static type S in the script. Let further
be J the set of interface implemented by T which are not implemented by S
already. For each interface I in J which has no super type I' of I in J a
implicit conversion from S to I is inserted into the preamble.
Michael
[1] https://issues.apache.org/jira/browse/SLING-1236
