Aug 19
For some people the Yielder test cases didn’t pass properly. Readers Hanson Char and Michael Barker found a bug, which is either caused by the different OS used or the different compiler used (Windows vs. Linux/Mac, or Eclipse vs. Sun/Apple compiler).
At the moment I’m relying on the aforementioned people to help with the bug, as I don’t have a testing ground for it myself – I’m creating one at the moment so that for future bugs I’ll be able to test them through. In the meantime, I’ve started a Google Group for yielder-related discussions so it will be easier to raise problems and collaborate on these sorts of bugs (and hopefully, also collaborate on ideas of how to use this feature).
So thanks, and keep the good (and bad) feedback coming!
Liked Chaotic Java? It's free! But maybe you can
August 19th, 2007 at 7:47 am
[...] University of Washington Yielder: Eclipse bug revealed, newsgroup created » This Summary is from an article posted at Chaotic Java on Sunday, August 19, 2007 For some people the Yielder test cases didn’t pass properly. Readers Hanson Char and Michael Barker found a bug, which is either caused by the different OS used or the different compiler used (Windows vs. Linux/Mac, or Eclipse vs. Sun/Apple compiler Summary Provided by Technorati.comView Original Article at Chaotic Java » 10 Most Recent News Articles About Washington State University [...]
August 28th, 2007 at 1:25 pm
[...] One of the latest discovered bugs in Yielder, originally thought to be linked to Eclipse, is apparently related to the debugging information usually supplied by compilers. The lack of debugging information made promoting local variables to class members impossible with the current way the yielder works, and new approaches are much more complex. [...]