Mercurial
hg/apidesign
/ file revisions
summary
|
shortlog
|
changelog
|
graph
|
tags
|
bookmarks
|
branches
|
file
| revisions |
annotate
|
diff
|
rss
|
help
(0)
tip
samples/gc/test/org/apidesign/gc/CompilerSurprisesTest.java
Wed, 29 Oct 2008 18:10:24 +0100
Too long line
file
|
diff
|
annotate
Wed, 29 Oct 2008 17:41:37 +0100
Petr Nejedl? discovered that surrounding variable definition with { } does not guarantee it to be removed from stack
file
|
diff
|
annotate
Fri, 17 Oct 2008 09:23:37 +0200
Wrong English in method name
file
|
diff
|
annotate
Fri, 17 Oct 2008 09:01:08 +0200
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.
file
|
diff
|
annotate
Wed, 15 Oct 2008 21:48:18 +0200
Too long lines
file
|
diff
|
annotate
Wed, 15 Oct 2008 21:39:35 +0200
Renaming the class and adding code snippet boundaries
file
|
diff
|
annotate
(0)
tip