The code below catches the exception to write out a log statement and then re-throws the same exception. It is recommended to let the caller decide if the message should

Avoiding null pointer exceptions is a good programming practice. However, simple things such as string comparison can also lead to null pointer exceptions. Considering the following: You have a constant

There are times when we need to reflect the changes made to a file in a different file as well. Mostly, they are made available in a common place so

for (float f = 10f; f!=0; f-=0.1){ System.out.println(f);} The code above causes an endless loop, it doesn’t act as expected, because 0.1 is an infinite binary decimal and f will

In equal comparisons it is recommended to place literals first. This way you eliminate the risk of NullPointerException: //avoid obj.equals(“foo”);//prefer”foo”.equals(obj); Related Articles Using the “==” Operator with Double or Float

Java long behaves differently when used with the letter L and without it. Code snippet public class JavaLong{ public static void main(String args[]) { JavaLong javaLong = new JavaLong(); javaLong.proceed();

Annotations are similar to interfaces in that you can convey your own specifications that others will need to follow. Here we are defining an Annotation named ClassHeaderAnnote, which has few