Scala Language

Hi,

Since we are already providing convenient converters, can we add java.util.Enumeration<T> and java.util.Iterator<T> to the Converstions implicit list? I find this useful when working with java libraries.

Also while we are on the topic, is there reason why scala.collection.jcl.IterableWrapper accepts java.util.Collection as underlying object and not the java.util.Iterable as the class name suggested? This is confusing to user.

Thanks,
Zemian
--
http://www.jroller.com/thebugslayer

This release is primarily just a few small bugfixes, so I gave it a
micro dot.

Configgy is a library for handling config files and logging for a scala
daemon.

Java has the nice property of mapping very well to UML class diagrams.
Has anyone thought about how well they can represent all the possible
Scala types or if not, then how to do diagrams for Scala code?

For example:

trait BaseComponent { self: Composite => }
trait BaseComposite extends BaseComponent

trait SpecializedComponent { self: SpecializedComposite => }
trait SpecializedComposite extends BaseComposite with SpecializedComponent

How to represent this? I came up with the following (see attached PNG)

Erkki

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Speaking of announcements we have been using a HTTP library for our
commercial web development for some time.

Hi all,

First off, let's consider this to be a round up for new blogs. If you have or know of a scala blog that isn't on planet scala and you want it added, let me know and I will do so.

Secondly, I have a question about the sort of content that shows up on it. As you may have noticed, there's a reasonable amount of non scala related content on there - mainly Java and Haskell, but also Ruby, many other languages and an occasional sprinkling of personal content. Personally, I'm totally ok with that.

I would like to announce the first release of sbt, a build tool for Scala that
aims to do the basics well.