Throw an AssertionError explicity?

[Yeming Hu]

In the K&B bonus master exam, we have the following question:

Which are true? (Choose all that apply.)
A It's not good practice to place assertions where you think execution where you think execution should never reach.

B It is sometimes appropriate to call getters and setters from assertions.

C Use assertions to verify the arguments of private methods.

D Assertions can be disabled for a particular class.

E Never throw an AssertionError explicitly.

The given answer is C && D. I think E is also right. Could you guys give me an example where we need to throw an AssertionError explicitly?

Thanks,

[Rahul Siddharth]

The answer in the book is correct."Throw" should not be associated with Assertions(Bad practice).Assertions are to help you test your assumptions and tell you if you are wrong.They return false in such case.If you are trying to "Catch" the error ,as a programmer you have coded wrongly.Therefore "handling" beats the whole point of assertions.

[Yeming Hu]

Originally posted by rahul siddharth:
The answer in the book is correct."Throw" should not be associated with Assertions(Bad practice).Assertions are to help you test your assumptions and tell you if you are wrong.They return false in such case.If you are trying to "Catch" the error ,as a programmer you have coded wrongly.Therefore "handling" beats the whole point of assertions.

Didn't get you. It seems you agree with the point we should never throw AssertionError. Therefore the E should be a correct answer.

[Remko Strating]

the following link within the Ranch has an equal discussion so you could have a look at it

Throw Assertions Explicit

[Yeming Hu]

Originally posted by Remko Strating:
the following link within the Ranch has an equal discussion so you could have a look at it

Throw Assertions Explicit

Thanks a lot!