VirtualBox和Rails服务器上的Ubuntu(Ubuntu on VirtualBox and Rails server)

 包对象被转换为名为package.class IIRC的普通java类文件。 从那时起，我假设它的行为与任何普通的Java类一样，因此它在首次引用时被加载并实例化。 在Scala中，这意味着您需要在包对象中定义一些方法或val ，然后从外部访问它。 在您的情况下，您可以尝试从Classy的构造函数或实例化Classy的代码中调用它。 
 
 更新 
 
 好的，这是我运行的一些代码来测试我上面描述的内容： 
 
// package.scala
package some

package object pkg {
  println("package created!")

  def func() { println("func called") }
}

// C.scala
package some.pkg

class C {
  println("created C")
}

// G.scala
package some.pkg

object G {
  println("creating G")
  func()
  println("created G")
}

// PackageTester.scala
package some.pkg

object PackageTester extends App {
  val c = new C
  val g = G
}
 
 输出是： 
 
created C
creating G
package created!
func called
created G
 
 这证明Scala包对象是懒惰创建的，只有在它们被实际引用时才会创建。 事实上，对于“普通”Scala对象也是如此，如上面的G所示。 

The package object is translated into a normal java class file called package.class IIRC. From then on I assume it behaves like any normal Java class, thus it is loaded and instantiated when it is first referenced. In Scala, that means you need to define some method or val in the package object, then access it from outside. In your case, you may try calling it from the constructor of Classy, or from the code which instantiates Classy.
 
Update
 
OK, here is some code I ran to test what I described above:
 
// package.scala
package some

package object pkg {
  println("package created!")

  def func() { println("func called") }
}

// C.scala
package some.pkg

class C {
  println("created C")
}

// G.scala
package some.pkg

object G {
  println("creating G")
  func()
  println("created G")
}

// PackageTester.scala
package some.pkg

object PackageTester extends App {
  val c = new C
  val g = G
}
 
And the output is:
 
created C
creating G
package created!
func called
created G
 
Which proves that Scala package objects are created lazily, only when they are actually referenced. And in fact the same is true for "normal" Scala objects, as demonstrated by G above.