John, Good that you ask. There are two reasons.
First, my personal goal is to gain a deeper understanding of the Scala language (building the translator does force me to think about Scala semantics). Second, some very smart GWT users have tried a number of approaches [1] without decisive success. So the problem appears interesting and its solution may be useful. This project does not aim to enthrone the bytecode generator, nor to achieve binary compatibility with the resulting .class files. So in this sense, yes, the "user base" one can anticipate for my translator is (way) smaller than for the Scala compiler. But still, it's not only for fun :-) [1] Discussion at GWT Contributors, http://groups.google.com/group/google-web-toolkit-contributors/search?group=google-web-toolkit-contributors&q=scala
-- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
