Jaroslav Tulach <jtulach@netbeans.org> [Sun, 09 Nov 2008 16:20:01 +0100] rev 291
Renaming arguments
Jaroslav Tulach <jtulach@netbeans.org> [Sun, 09 Nov 2008 15:44:53 +0100] rev 290
Showing API for AServerInfo
Jaroslav Tulach <jtulach@netbeans.org> [Wed, 29 Oct 2008 18:10:24 +0100] rev 289
Too long line
Jaroslav Tulach <jtulach@netbeans.org> [Wed, 29 Oct 2008 17:41:37 +0100] rev 288
Petr Nejedl? discovered that surrounding variable definition with { } does not guarantee it to be removed from stack
Jaroslav Tulach <jtulach@netbeans.org> [Fri, 24 Oct 2008 21:15:50 +0200] rev 287
Moving into real packages
Jaroslav Tulach <jtulach@netbeans.org> [Fri, 24 Oct 2008 12:07:34 +0200] rev 286
Rewriting the initialization to be more meaningful for clueless reader that does not need to understand every detail
Jaroslav Tulach <jtulach@netbeans.org> [Fri, 24 Oct 2008 11:32:33 +0200] rev 285
extracting the accessor initialization outside of the API block of the Item class
Jaroslav Tulach <jtulach@netbeans.org> [Fri, 17 Oct 2008 09:23:37 +0200] rev 284
Wrong English in method name
Jaroslav Tulach <jtulach@netbeans.org> [Fri, 17 Oct 2008 09:01:08 +0200] rev 283
ljnelson noted at 'http://weblogs.java.net/blog/jst/archive/2008/10/the_better_comp.html' that it is enough to make the variable final and the problem goes away. True, final helps, however the same code without final works as well. This very likely means that the compiler puts the variable into the topmost block where it is guaranteed to be fully initialized. That is why we need a hint warn about declaration of non-fully initialized variables.
Jaroslav Tulach <jtulach@netbeans.org> [Wed, 15 Oct 2008 21:48:18 +0200] rev 282
Too long lines