-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I love GHC's Trac, I was wondering if there could be some such thing for jhc (not that I have any tickets for it yet, but I might once I get a computer powerful enough to start hacking jhc :) Isaac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGQF4vHgcxvIWYTTURAhWHAJ9i/HYIX6s2VWKS8qDUawwx1/vuKACg07iM rWij5T0vnSUBMI/L/ZBJAk0= =ToVL -----END PGP SIGNATURE-----
On Tue, May 08, 2007 at 07:25:36AM -0400, Isaac Dupree wrote:
I love GHC's Trac, I was wondering if there could be some such thing for jhc (not that I have any tickets for it yet, but I might once I get a computer powerful enough to start hacking jhc :)
There isn't one set up now, most bugs tend to be very obvious due to jhc just not working :) But if someone wanted a trac or bugzilla database, I could go about setting one up. Perhaps a section of the haskell wiki for jhc is in order, like some other compilers have. Jhc's full program analysis is sort of a mixed blessing when it comes to bugs. Since every compile goes through all the standard libraries, and the standard libraries excercise pretty much every aspect of the compiler, it turns every compilation of 'Hello World!' into a full on regression test. On one hand, it makes bugs very shallow, on the other, it means that bugs are very hard to work around, as you can't just avoid using the offending bit of code that triggers the bug as it is in the library somewhere. John -- John Meacham - ⑆repetae.net⑆john⑈
participants (2)
-
Isaac Dupree -
John Meacham