Actually I\'m developing a compiler plugin for Scala according to the article on http://www.scala-lang.org/node/140.
Here is the code of the plugin:
You can invoke the Scala compiler, plus plugins, programmatically with code like the following:
import scala.tools.nsc.{Settings, Global}
import scala.tools.nsc.io.VirtualDirectory
import scala.tools.nsc.reporters.ConsoleReporter
import scala.tools.nsc.util.BatchSourceFile
// prepare the code you want to compile
val code = "object Foo extends Application { println(42 / 0) }"
val sources = List(new BatchSourceFile("", code))
val settings = new Settings
// save class files to a virtual directory in memory
settings.outputDirs.setSingleOutput(new VirtualDirectory("(memory)", None))
val compiler = new Global(settings, new ConsoleReporter(settings)) {
override protected def computeInternalPhases () {
super.computeInternalPhases
for (phase <- new DivByZero(this).components)
phasesSet += phase
}
}
new compiler.Run() compileSources(sources)
Note that this code requires that scala-compiler.jar
and scala-library.jar
be on the classpath when executing the code. If you are running your tests from within something like SBT, this will unfortunately not be the case.
To get things running from within SBT, you have to do some hoop jumping:
val settings = new Settings
val loader = getClass.getClassLoader.asInstanceOf[URLClassLoader]
val entries = loader.getURLs map(_.getPath)
// annoyingly, the Scala library is not in our classpath, so we have to add it manually
val sclpath = entries find(_.endsWith("scala-compiler.jar")) map(
_.replaceAll("scala-compiler.jar", "scala-library.jar"))
settings.classpath.value = ClassPath.join((entries ++ sclpath) : _*)
If you are running from within some other build environment, you might find that scala-library.jar
is already on the classpath, or if you're really lucky, then everything you need is on the standard Java classpath, in which case you can replace the above with:
val settings = new Settings
settings.usejavacp.value = true
You can print out the value of the Java classpath with System.getProperty("java.class.path")
and you can of course print out entries
from the above code to see the classpath used by the class loader that is loading your test code.