Lots of people say that sort of thing, but it's imprecise. It is possible for a class to implement multiple interfaces, but the classical (pre‑Java8) interface had only abstract methods, so its implementing classes inherited only constants and empty methods. Even nowadays you can only regard constants and public default methods as having inherited implementations.
Royal Summers wrote:. . . "Interfaces allow for multiple inheritances, whereas classes do not." . . .
Hahahahahahahahaha! Yes, that does make sense, as long as you remember it is imprecise.
Royal Summers wrote:. . . i'll take imprecise if I can understand it over precise but I don't understand it . . .
That's a pleasure
. . . thanks. . . .
Royale Summers wrote:
Here's the explanation from my Bootcamp:
"Interfaces are classes that define method signatures and rely on classes to implement the code inside of them. It may be tempting to allow classes to inherit (extend) from the parent class and use @Override to change every method. However, this approach has fundamental issues of repeating oneself and the consequence of forgetting to override a critical method. Classes cannot implement some of the methods in the interface class but instead must implement all of them. One benefit of using Eclipse is that it will prompt (via an error message) to define a method if it is missing."