This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Some bugs in Java 7 that programmers' programming should avoid (Please share)...
I did find this one web site that had a bunch of bugs. I can't find it now. I think this would be useful to Java 7 programmers so they know what to avoid until they are fixed...
“Don’t worry if it doesn’t work right. If everything did, you’d be out of a job.” (Mosher's Law of Software Engineering)
“If debugging is the process of removing bugs, then programming must be the process of putting them in.” (Edsger Dijkstra)
There is indeed a bug caused by aggressive optimization done by the jvm. However in my opinion this shouldn't be a reason for not using Java SE 7. The fault only appears in certain situations and can be totally avoided by setting a flag.
"Any fool can write code that a computer can understand. Good programmers write code that humans can understand." --- Martin Fowler
Please correct my English.
I do know that features aren't bugs and vice versa. I just did not put quotes around the word "features". I do know a little of the optimization bug. It has something to do with loops. I wan't specifically talking about that one. I was talking about them all in general. Like, including that one, but not specifically that one bug. I found a website that had like 20 bugs or something found in Java. They were explained and it looked legit. If you can think of any others, that would be appreciated. If you could give an example and a fix, that would be even better. If you could give an example of the above optimization bug and how to fix it, that would be great. By "example", I mean code in relevant bugs.