If the parent class doesn’t have a no-argument constructor and the child doesn’t define any constructors, then the child class will not compile.
If the parent class doesn’t have a no-argument constructor but has at least one non-no-argument constructor, and the child doesn’t define any constructors, then the child class will not compile.
RTFJD (the JavaDocs are your friends!) If you haven't read them in a long time, then RRTFJD (they might have changed!)
Jesse Silverman wrote:No. The second statement adds complexity but no new value
If the parent class doesn’t have a no-argument constructor and the child doesn’t define any constructors, then the child class will not compile.
If the parent class doesn’t have a no-argument constructor but has at least one non-no-argument constructor, and the child doesn’t define any constructors, then the child class will not compile.
RTFJD (the JavaDocs are your friends!) If you haven't read them in a long time, then RRTFJD (they might have changed!)
Charles O'Leary wrote:
If the parent class doesn’t have a no-argument constructor and the child doesn’t define any constructors, then the child class will not compile.
More precise?
If the parent class doesn’t have a no-argument constructor but has at least one non-no-argument constructor, and the child doesn’t define any constructors, then the child class will not compile.
Cow telling her family history: “My grandfather was a knight. He was Sir Loin.”
Jesse Silverman wrote:I wasn't trying to be snarky
RTFJD (the JavaDocs are your friends!) If you haven't read them in a long time, then RRTFJD (they might have changed!)
Jesse Silverman wrote:I complained about the wording
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |