allan.jacobs@Eng 1997-10-30

A small number of bugs involve codes that looks like those included below.
They involve the interaction between abstract methods, packages, and
inheritance.  The issues have been outstanding for just about 1 year.

Should the following code be rejected at compile-time?
My 2 cents:
An abstract class is in one package.  A class that extends the abstract
class is in another package.  All abstract methods in the abstract class
have default access control, so they are inaccessible to the child class.
Because they are inaccessible, it seems like the child should not inherit
the abstract methods and therefore not be abstract at all.

    package p1;
    public abstract class Broken {
        abstract void f (); // default access
    }

    package p2;
    class TimeBomb extends p1.Broken {
                            // TimeBomb does not implement void f().
    }

Should the following code be rejected at compile-time?
My 2 cents:
An abstract class is in one package.  A class that extends the abstract
class is in another package.  All abstract methods in the abstract class
have default access control, so they are inaccessible to the child class.
Because they are inaccessible, it seems like the child should not inherit
the abstract methods.  An attempt to hide an inaccessible method should
succeed.

    package p1;
    public abstract class Broken {
        abstract void f (); // default access
    }

    package p2;
    class TimeBomb extends p1.Broken {
        void f () {
        }
    }