Make all numeric coercions explicit.

Optimistically, this is preparation for a day when we don't
let numeric types drift with the winds. Even without the optimism
it's a good idea. It flushed out an undocumented change in
the math package object relative to the methods being forwarded (a
type is widened from what is returned in java) so I documented
the intentionality of it.

Managing type coercions manually is a bit tedious, no doubt,
but it's not tedious enough to warrant abandoning type safety
just because java did it.

Author: paulp

src/library/scala/xml/include/sax/XIncluder.scala

@@ -95,7 +95,7 @@ class XIncluder(outs: OutputStream, encoding: String) extends ContentHandler wit
         // However, it is required if text contains ]]>
         // (The end CDATA section delimiter)
         else if (c == '>') out.write(">")
-        else out.write(c)
+        else out.write(c.toInt)
         i += 1
       }
     }

src/library/scala/xml/persistent/CachedFileStorage.scala

@@ -112,7 +112,7 @@ abstract class CachedFileStorage(private val file1: File) extends Thread {
   override def run = {
     log("[run]\nstarting storage thread, checking every "+interval+" ms")
     while (true) {
-      Thread.sleep( this.interval )
+      Thread.sleep( this.interval.toLong )
       save()
     }
   }