| Summary: | member type access not respected | ||
|---|---|---|---|
| Product: | gcc | Reporter: | Tom Tromey <tromey> |
| Component: | java | Assignee: | Not yet assigned to anyone <unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | gcc-bugs, java-prs |
| Priority: | P3 | Keywords: | accepts-invalid |
| Version: | 3.4.0 | ||
| Target Milestone: | 4.3.0 | ||
| Host: | Target: | ||
| Build: | Known to work: | ||
| Known to fail: | Last reconfirmed: | 2005-07-23 05:27:22 | |
| Bug Depends on: | 28067 | ||
| Bug Blocks: | 13607 | ||
Still exits on the mainline (20030525). There are couple of bugs like this one, I wondering if they will ever get fixed? Nobody knows... I suppose someone will fix these bugs when they become important for some reason. I know the package-private bug is in process at least. All gcj front end bugs have been fixed by the gcj-eclipse branch merge. I'm mass-closing the affected PRs. If you believe one of these was closed in error, please reopen it with a note explaining why. Thanks. |
Right now gcj will let a subclass see member type defined in a superclass, even if that member type has default access protection and the two classes are in different packages. For instance, this code compiles but should not. package one; import two.*; public class o extends t { boolean doit(Object x) { return x instanceof Res; } } package two; public class t { class Res { } } Release: unknown