Re: Guile 1.5.4 beta ready for testing.

[Marius Vollmer]

Keith Wright <address@hidden> writes:

> > Cc: address@hidden, address@hidden, address@hidden
> > From: Marius Vollmer <address@hidden>
> > 
> > Keith Wright <address@hidden> writes:
> > 
> > >   Bug: A bad .guile file kills the whole interpreter with
> > >     a message that does not mention .guile.
> > 
> > Running guile with the --debug option gives you a backtrace for errors
> > in ~/.guile.  Is that OK?
> 
> It's OK.  I wish I had known to do that when I had the problem.
> What about making that the default and let people who know
> every option and never make mistakes set --no-debug?
> ...or turn it off in their .guile file!

Hmm, well.  I'm tempted to say, yes, why not.  It will make Guile
slower by default (about twice as slow), but I find that I turn the
debugger on in my programs anyway, and then just leave it on.  The
slowness hasn't hurt me yet.

What do people say?  Should we turn debugging on by default, and make
the speed freaks turn it off explicitely?