diff options
author | Jason Zaugg <jzaugg@gmail.com> | 2013-12-17 17:47:15 +0100 |
---|---|---|
committer | Jason Zaugg <jzaugg@gmail.com> | 2013-12-18 14:29:17 +0100 |
commit | 7e85b595502974bebf2f2625c6bc3645f0d3ab27 (patch) | |
tree | 842325683b4d5458e1ae639718a75c3bc32d25f7 /test/files/presentation/t8085b.check | |
parent | a12dd9c3b6fb4a767eec8f6d3bf0a9a2266eff85 (diff) | |
download | scala-7e85b595502974bebf2f2625c6bc3645f0d3ab27.tar.gz scala-7e85b595502974bebf2f2625c6bc3645f0d3ab27.tar.bz2 scala-7e85b595502974bebf2f2625c6bc3645f0d3ab27.zip |
SI-8085 Fix BrowserTraverser for package objects
A source file like:
import foo.bar
package object baz
Is parsed into:
package <empty> {
import foo.bar
package baz {
object `package`
}
}
A special case in Namers compensates by adjusting the owner of
`baz` to be `<root>`, rather than `<empty>`.
This wasn't being accounted for in `BrowserTraverser`, which
underpins `-sourcepath`, and allows the presentation compiler to
load top level symbols from sources outside those passes as
the list of sources to compile.
This bug did not appear in sources like:
package p1
package object p2 { ... }
... because the parser does not wrap this in the `package <empty> {}`
This goes some way to explaining why it has gone unnoticed for
so long.
Diffstat (limited to 'test/files/presentation/t8085b.check')
-rw-r--r-- | test/files/presentation/t8085b.check | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/test/files/presentation/t8085b.check b/test/files/presentation/t8085b.check new file mode 100644 index 0000000000..79c1b2aa17 --- /dev/null +++ b/test/files/presentation/t8085b.check @@ -0,0 +1,3 @@ +reload: NodeScalaSuite.scala +open package module: package nodescala +Test OK |