Hi Neil, Neil Jerram <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Ludovic Courtès) writes: >> (I had forgotten about it, which may be an indication that we should >> really start using the bug tracker.) > > What would that involve? Not much actually. Just mention it in the relevant pieces of documentation. The bug tracker automatically sends emails to `bug-guile' when new bugs are reported or when the status of existing bugs changes. We can also assign a bug to a specific developer, which can help coordinate efforts. > Yes, I meant to do that but forgot. No need for with-output-to-port > though; just need to change the second arg of display-backtrace to > (%make-void-port "w"). Right. > I looked at that, but couldn't work out what unmemoize-expr's args > should be. Also, this would make the test depart further from the > reported scenario. So I think best to stick with using > display-backtrace. OK. > Yes, I'll do that. There's a couple of places in the tests that use > debug-enable/disable like this, so it's worth adding a > with-debugging-evaluator form to (test-suite lib). Yes, makes sense. Can you also add a `NEWS' entry? Thanks, Ludovic. _______________________________________________ Bug-guile mailing list Bug-guile@gnu.org http://lists.gnu.org/mailman/listinfo/bug-guile
