Skip to main content

An article that has sparked my interest in Java 8 ...

This excellent article from Zeroturnaround about how Java 8 could transform your code base has finally got me intrigued about Java 8.

At work we use Java 6 everywhere and that was a struggle to get them to upgrade to that, luckily they have made noises about maybe moving to Java 7 this or next year. Some guys that are thinking of getting Java certification are going for the Java 6 route, whereas I am more interested in how the new Java 7 features can help us. But even Java 7 isn't new. Companies move a lot slower to adopt new versions of Java perhaps.

http://zeroturnaround.com/rebellabs/what-migrating-to-java-8-will-do-to-your-codebase-a-practical-example/

IMHO, Java 8 looks set to revolutionise Java.

JavaOne 2013 Roundup: Java 8 is Revolutionary, Java is back


Labels:

Popular posts from this blog

Overcome Java JNI gdb errors on GNU/Linux

If you happen to try to debug any Java JNI programs using gdb on GNU/Linux you will soon come across error messages. For example : $ gdb --args java MyJavaProgramUsingJNI cannot find user-level thread for LWP nnn: generic error warning: Cannot initialize thread debugging library: versions of libpthread and libthread_db do not match The reason for this is that the java program mucks around with LD_LIBRARY_PATH and that prevents gdb from running correctly. To overcome this, you have to run your Java program and place a pause in the Java code, such as reading a key, and then in another shell, run gdb to attach to the running Java process. You can then set your breakpoint on your JNI code and debug it. Here is an example : Compile your Java program: $ javac JNITest.java Generate the JNI header file: $ javah -jni JNITest.java Create and compile your C code library: $ cat jnilib.c #include "JNITest.h" JNIEXPORT jint JNICALL Java_JNITest_addValues( JNIEnv...
Read more