Posts

Get current executing method name in Java

//Get method name using Java.lang.Class.getEnclosingMethod()
    public static void getMethodNameUsingClassInstance() {         String methodNameUsingClassInstance =             new Object() {}.getClass().getEnclosingMethod().getName();         System.out.println("Current Method Execution Name Using Class Instance - " +             methodNameUsingClassInstance);     }

//Get method name using StackTraceElement.getMethodName()
    public static void getMethodNameUsingStackTraceElement() {         StackTraceElement stackTraceElements[] = (new Throwable()).getStackTrace();         System.out.println("Current Method Execution Name Using StackTraceElement - " +             stackTraceElements[0].getMethodName());     }

//Get method name using Thread.currentThread().getStackTrace()
    public static void getMethodNameUsingCurrentThread() {         System.out.println("Current Method Execution Name using Current Thread - " +             Thread.currentThread().getStackTrace()[1].ge…

Java Comment //$NON-NLS-1$

$NON-NLS x$ is specifically for externalization and internationalization. It marks a string as being inappropriate for externalization. Eclipse and potentially other IDEs can be configured to present warnings when strings are hardcoded into a program so that programmers remember to externalize. NLS stands for National Language Support.


The number after $NON-NLS- signifies which string on the tagged line the tag is for. The number 1 works for you, likely because there is only 1 string on the line your are trying to tag.
If you had 2 strings on the same line, you can, for example, tag only the second string using $NON-NLS-2$.
//Warning on "baz" foo("bar","baz"); //$NON-NLS-1$
//Warning on "bar" foo("bar","baz"); //$NON-NLS-2$
//No warnings foo("bar","baz"); //$NON-NLS-1$  //$NON-NLS-2$
//Warning on "baz" (apparently the slashes are required even with multiple tags) foo("bar","baz&quo…

Create Runnable Jar - Eclipse Options

When exporting to a Runnable Jar, there are three options in eclipse Helios. Extract required libraries into JARPackage required libraries into JARCopy required libraries into sub folder next to JAR. What are differences : Extract required libraries into JAR - Extracts the actual .class files from the libraries your app uses and puts those .class files inside the runnable JAR. So, the runnable JAR will not only contain the .class files of your application, but also the .class files of all the libraries your application uses. Package required libraries into JAR - Puts the actual JAR files of the libraries into your runnable JAR. Normally, a JAR file within a JAR file cannot be loaded by the JVM. But Eclipse adds special classes to the runnable JAR to make this possible. Copy required libraries into sub folder next to JAR - Keeps the library JARs completely separate from the runnable JAR, so the runnable JAR will only contain the .class files of your application. Option #2 is convenient be…

Java toString()

toString()
public String toString() { StringBuilder builder = new StringBuilder();
try { Class e = Class.forName(this.getClass().getName()); builder.append(this.getClass().getSimpleName() + " [ ").append( System.getProperty("line.separator"));
while (e.getSuperclass() != null) { Field[] aClassFields = e.getDeclaredFields(); Field[] arg3 = aClassFields; int arg4 = aClassFields.length;
for (int arg5 = 0; arg5 < arg4; ++arg5) { Field field = arg3[arg5]; field.setAccessible(true); builder.append("\t") .append(field.getName()) .append(" = ") .append(field.getName() .matches("(?i:.*password.*)") ? "<password_field>" : field.get(this)).append(",") .append(System.getProperty("line.separator")); }
e = e.getSuperclass(); }
builder.append("]"); } catch (Exception arg7) { arg7.printStackTrace(); }
return builder.toString(); }

Little Endian and Big Endian

Image
Little and big endian are two ways of storing multibyte data-types ( int, float, etc). In little endian machines, last byte of binary representation of the multibyte data-type is stored first. On the other hand, in big endian machines, first byte of binary representation of the multibyte data-type is stored first.

Suppose integer is stored as 4 bytes (For those who are using DOS based compilers such as C++ 3.0 , integer is 2 bytes) then a variable x with value 0×01234567 will be stored as following.
Memory representation of integer ox01234567 inside Big and little endian machines

How to see memory representation of multibyte data types on your machine?
Here is a sample C code that shows the byte representation of int, float and pointer. #include <stdio.h>