Investigate status of scala.mobile #4505
Comments
|
Imported From: https://issues.scala-lang.org/browse/SI-4505?orig=1 |
|
@soc said: // source 'class A { ... }' becomes in bytecode: interface A.class + class A$$class.class
// source 'object A { ... }' becomes in bytecode: interface A.class + class A$$.class
val append = if (loader.loadClass(className).isInterface) "$$class" else "$$"When did Scala actually change the classname mangling? It is certainly before I started looking at Scala during 2.7.x. This code obviously hasn't worked since a long time, isn't used anywhere and mainly just throws exceptions. Maybe this is a candidate for a "quick delete"? |
|
Trond Olsen (tolsen77) said: |
|
@soc said: |
|
@magarciaEPFL said: |
|
@soc said: |
|
@SethTisue said: |
= problem =
scala.mobile seems to be of little use, considering all the boxing/implicit/type/... magic happening in the compiler.
In fact when investigating, I couldn't find a single example of how to use it with the Scala library ... without getting (
"java.lang.RuntimeException: class <something> has no public constructor")There seems to be no way to actually instantiate a "Location" properly and the way to get the "standard constructor" seems seriously broken (
cs(0).newInstance("")... since when do we expect that classes have a constructor taking a String? Expecting them to have a empty standard constructor, yes, but ""?)= analysis =
This code is seriously broken.
Considering there are actually no tests which could help figuring out what is supposed to work and what is not and classes which need related functionality like scala.testing.Show don't even use it at all and roll their own invocation scheme instead, there just be serious thoughts about how long scala.mobile should still be living.
(The name is also pretty bad ... I can't see how anyone will first expect some JavaME/handset related functionality in it ...)
Actually every use cases in the documentation refers to some non-existing jar file, which makes it impossible to actually understand what the use cases are about.
= enhancement recommendation =
Figure out what this classes are supposed to do, document it and write tests for it ... if that doesn't work, maybe deprecate and remove it?
I just checked Google and I found not a single case of code using this class or even a question about it.
The text was updated successfully, but these errors were encountered: