- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
three little problems
Mon, 2010-01-11, 15:46
In a previous discussion on "Scala to Java" three situations were mentioned
whose resulting bytecode has no obvious counterpart in Java :
(a) blocks as part of expressions that are executed with non-empty stacks.
(b) object initialization, where outer pointers have to be assigned before
calling the superclass
(c) Overrides in parametric classes require sometimes bridge methods which
can lead to double denitions when seen as Java source.
I *could* make progress on dealing with them (first of all, understanding
the problems) if someone were so kind to point me to the locations in
GenJVM (or GenICode) where the *bytecode version* for the above situations
is emitted. With that, I'll tryto connect the dots to the Java counterpart.
Your efforts will be rewarded! I'll post my findings in an upcoming
write-up, with credits and everything.