Comments on: Nabaztag Scala Library http://morlhon.net/blog/2009/11/09/nabaztag-scala-library/ Jean-Laurent de Morlhon weblog Thu, 03 Feb 2011 20:29:19 +0000 hourly 1 http://wordpress.org/?v=3.1 By: @sadache http://morlhon.net/blog/2009/11/09/nabaztag-scala-library/comment-page-1/#comment-1272 @sadache Fri, 13 Nov 2009 11:22:31 +0000 http://morlhon.net/blog/?p=279#comment-1272 The issue is much simpler than this. Imagine any library writer that uses internally other date type than Java's broken Date (JodaTime for instance): If he doesn't wrap it back into Java broken Date then you have no choice but to download and use JodaTime apis, period. It is a design issue and by no way a Scala problem. In your Scala code you could just use the available Java List but you won't since it is really less interesting. The call is difinitively yours :) The issue is much simpler than this. Imagine any library writer that uses internally other date type than Java’s broken Date (JodaTime for instance): If he doesn’t wrap it back into Java broken Date then you have no choice but to download and use JodaTime apis, period.

It is a design issue and by no way a Scala problem. In your Scala code you could just use the available Java List but you won’t since it is really less interesting.

The call is difinitively yours :)

]]> By: Fanf http://morlhon.net/blog/2009/11/09/nabaztag-scala-library/comment-page-1/#comment-1268 Fanf Mon, 09 Nov 2009 21:48:16 +0000 http://morlhon.net/blog/?p=279#comment-1268 Hey, happy to know that there are other OSSGTP Scala fans :) For your problem of Java interfacing, I would say that the "Java interface binding" is the better way to go. I tried the other way around, and you end missing a lot of Scala-ism due to the mix with Java-fashion in the Scala part. Moreover, in Scala 2.8, scala.collection.JavaConversions really help in converting between Java and Scala collections (and so, a slim Java binding interface is not too painful to build). And finally, the Scala list is a pure functional structure: nearer to Java ArrayList is Scala 2.8 Buffer. See you next time around a beer ;) Hey, happy to know that there are other OSSGTP Scala fans :)

For your problem of Java interfacing, I would say that the “Java interface binding” is the better way to go.
I tried the other way around, and you end missing a lot of Scala-ism due to the mix with Java-fashion in the Scala part. Moreover, in Scala 2.8, scala.collection.JavaConversions really help in converting between Java and Scala collections (and so, a slim Java binding interface is not too painful to build).

And finally, the Scala list is a pure functional structure: nearer to Java ArrayList is Scala 2.8 Buffer.

See you next time around a beer ;)

]]>