Java Certification Resources and Java Discussion Forum
https://enthuware.com/forum/
Code: Select all
public void openSocket(int port){
assert port > 1000;
...
}It's not wrong to do assert on the parameter of a public method. I ran it and found no problem.Input params of a public method should not be validated using assertions.
Could you please tell me what you were trying to explain? I don't think I follow your explanation. Many thanks.3. Should not be used for side effects. For example:
public boolean doSomething(){
...
}
public void someMethod(){
assert doSomething();
}
This is not a proper use because here the assertion is used for its side effect of calling of the doSomething() method. The only case where this could be justified is when you are trying to find out whether or not assertions are enabled in your code:
boolean enabled = false;
assert enabled = true;
if(enabled) System.out.println("Assertions are enabled")
else System.out.println("Assertions are disabled")
The part it says "....the assertion is used for its side effect of calling of the doSomething() method."This is not a proper use because here the assertion is used for its side effect of calling of the doSomething() method. The only case where this could be justified is when you are trying to find out whether or not assertions are enabled in your code:
Side effect simply means that you are killing two birds with one stone. You want to achieve one thing by an assert statement but while doing so, you are also achieving something else. This will work only if assertions are enabled. Explained here: https://docs.oracle.com/javase/7/docs/t ... ssert.htmlschchen2000 wrote:The part it says "....the assertion is used for its side effect of calling of the doSomething() method."This is not a proper use because here the assertion is used for its side effect of calling of the doSomething() method. The only case where this could be justified is when you are trying to find out whether or not assertions are enabled in your code:
What does that part mean? In fact, I really did not follow the explanation.
It is not talking about enabling or disabling assertions in the code. It is talking about checking whether they are enabled or disabled in the code. They are indeed enabled/disabled from the command line but you can check i.e. find out within your code."....to find out whether or not assertions are enabled in your code"????
How do we enable assertions in our code? To the best of my knowledge, assertions are disabled or enabled from the command prompt when the program is run, i.e. using -ea or lack thereof in order to enable or disable the assertion respectively from the command line on a terminal.
Thanks.
Schmichael