Should scripts work with .scala files

[alvinj]

I was just wondering if .sc scripts are supposed to work with .scala files that are in the current directory, or in a resources directory?

I tried this, with both files in the same directory, and it didn’t work:

// Person.scala
case class Person(name: String)

// Test.sc
#!/usr/bin/env scala-cli
val p = Person("Jane")
println(p.name)

Then I tried this and it also didn’t work:

// resources/Person.scala
case class Person(name: String)

// Test.sc
#!/usr/bin/env scala-cli
// using resourceDir "./resources"
val p = Person("Jane")
println(p.name)

That second attempt results in this error:

$ ./TestPerson.sc 
[error] ./TestPerson.sc:2:4: Unrecognized directive: using resourceDir ./resources
[error] // using resourceDir "./resources"
[error]    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This isn’t a huge deal, just a question. I didn’t know if scripts were meant to be totally included in one file, but then I saw that they work with jar files, so it made me wonder what the difference was between using a .scala file in the current directory (or a resources directory) compared to using a jar file. Thanks.

Totally unrelated, but it’s cool that using directives like these work:

// using options -deprecation -unchecked -feature -explain
// using jar stringutils_3-0.1.jar
// using javaOpt -Xms64M -Xmx128M

Once you get used to it, it’s a really clever idea.

[tpasternak]

Yep, thank you for pointing it out! We need to somehow document/clarify this.

The first example would work if you run scala-cli . or scala-cli Test.scala Person.scala. If you point to a single file, the other ones are not compiled

using resourceDir was not found because we have had documentation mismatch (same problem as here #432). In 0.0.9 it should be OK

[SethTisue]

Note that I also opened #466 which suggests that scripts with no file extension at all ought to be allowed.