unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Bugs <bug-guile@gnu.org>
Subject: Re: Bug #1 - (debug-disable 'debug) has no effect ...
Date: 15 Mar 2002 23:54:52 +0000	[thread overview]
Message-ID: <m3bsdpmlo3.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <877kodoa9g.fsf@zagadka.ping.de>

>>>>> "Marius" == Marius Vollmer <mvo@zagadka.ping.de> writes:

    Marius> Neil Jerram <neil@ossau.uklinux.net> writes:
    >> >>>>> "Marius" == Marius Vollmer <mvo@zagadka.ping.de> writes:
    >> 
    Marius> Neil Jerram <neil@ossau.uklinux.net> writes:
    >> >> 
    >> >> I'm not convinced.  How can people be expecting debugging to be turned
    >> >> on after having explicitly said `(debug-disable 'debug)' in their
    >> >> .guile file?
    >> 
    Marius> Because Guile behaved like that for quite a while.
    >> 
    >> But it's a bug!

    Marius> Yes, and it is fixed in the non-stable branch.  It's too late to fix
    Marius> it in the stable branch.  

    Marius> It is too late because I have decided so.  I know that this might not
    Marius> be popular, and it comes somewhat as a surprise.  I don't do this
    Marius> because I like to be despotic, but because I think it is constructive.
    Marius> 1.6 has been too long in the making.  Of course, there is a huge
    Marius> amount of improvements to be made in Guile, but that's why we have the
    Marius> unstable HEAD branch.

OK, fair enough.  Sorry for going on about this for so long.

    >> Do we say that we don't want to fix `(array? car) => #t)' now because
    >> Guile has behaved this way for a while?

    Marius> Yes, exactly.  It wont be fixed in the stable branch.

Sorry again; I didn't realize that we weren't planning to fix this in
the stable branch.  Understanding this makes the overall picture
much clearer. 

        Neil


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile


      parent reply	other threads:[~2002-03-15 23:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3sn7b6j64.fsf@laruns.ossau.uklinux.net>
     [not found] ` <87eliuzx1o.fsf@zagadka.ping.de>
     [not found]   ` <m38z927h1c.fsf@laruns.ossau.uklinux.net>
2002-03-14 23:11     ` Bug #1 - (debug-disable 'debug) has no effect Marius Vollmer
2002-03-14 23:57       ` Neil Jerram
2002-03-15 20:18         ` Marius Vollmer
2002-03-15 23:53           ` Neil Jerram
2002-03-16  0:13             ` Marius Vollmer
2002-03-15 23:54           ` Neil Jerram [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3bsdpmlo3.fsf@laruns.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=bug-guile@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).