Hi Sascha, I completely agree and support your wishes! In fact, it would be nice if the whole classpath and its documentation (javadoc) would be rebuilt on a regular base and offered through the website.
I disagree on one point: testing doesn't slow down development. It may be boring, but it is like a safety net that prevents developers from comitting buggy code and allow to detect errors early (and thus much faster) when they are inserted. -Patrik -------- Patrik Reali http://www.reali.ch/~patrik/ http://www.oberon.ethz.ch/jaos > Dear co-hackers, > > having read quite a bit of Classpath code, I'd like to express two wishes. > > First, please write more test cases. I agree that it is boring, dumb, and > taxing; testing slows down development. But it's also the most reliable > way to make sure that code really works. If anyone needs to change our > code in five years, they'll want to know whether their change has any > serious impact. Without a large test suite, this is close to impossible. > > Second, please write understandable documentation for every single > method. Developers should be able to create free programs without > referring to external documents. These could disappear at any time. > > In other words, I think that we really need to improve the quality of our > code. Building a sound foundation for others is not the same as some fun > week-end hack. > > Thank you all, > > -- Sascha > > Sascha Brawer, [EMAIL PROTECTED], http://www.dandelis.ch/people/brawer/ > > > > > _______________________________________________ > Classpath mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/classpath > > _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
