Blogs

It seems that Java debugger protocol (JVMTI) hasn't got good support for access to return value of function. This feature is supported for instance in Microsoft Visual C++, it is usually shown in the "variable's view" as a pseudo variable. The access to return value should be implemented in Java 6.0 (JDWP, JDI: Add return value to Method Exit Event), but it is inefficient and it requires setting up method tracing on method exits to be able to obtain the return value.

Static analysis tools may find code smell. But sometimes some trivial smells are not detected. For instance when you compile with Java 6.0 or Eclipse 3.4, FindBugs v1.3.8 will not find anything suspicious in this method:

When your build.xml is complex, it is not easy to read default Ant log output and understand which tasks are currently on the stack. You can use XmlLogger to the rescue (also works in Eclipse 3.4):

ant -logger org.apache.tools.ant.XmlLogger -logfile build_log.xml
(Details can be found at Ant listener)

For longer time I experiences unpleasant slow freeze of IE 7.0 each time I opened link in new tab and also closing IE took 20 and more seconds to finish.

The Java default collation rules ignore whitespaces. This is unfortunate because for instance Czech collation rules include spaces. The RuleBaseCollator uses CollationRules.DEFAULTRULES (SUN specific) and appends locale specific rules at the end. The default rules uses spaces in second order comparison. This can be fixed with two solutions:

Bellow are some basic information about OR mappers and random thoughts.

Here is a list of some command line parsers:

• Anyoption - simple and small but no types - all options are parsed as strings. Also no support for arguments without option.
• TCLAP - heavy, uses stdlib, support for types, extensive documentation
• SimpleOpt - small but ugly, no types