unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Compatibility V1.8 and 2.0 - deprecated (debug-enable 'debug)
Date: Mon, 22 Aug 2011 22:59:28 +0200	[thread overview]
Message-ID: <87y5yli2mn.fsf@gnu.org> (raw)
In-Reply-To: m362m6g2pl.fsf@harrington.peter-b.co.uk

Hi,

(Sorry for the late reply.)

Peter TB Brett <peter@peter-b.co.uk> skribis:

> Ian Hulin <ian@hulin.org.uk> writes:
>
>> In the Lilypond code we use (debug-enable 'debug) to give full error
>> information when we have Scheme lines embedded in a LilyPond source file.
>>
>> This option has been deprecated in V2.0 but there's no indication in
>> NEWS of how to supply equivalent functionality.
>
> I believe that it's always on in Guile 2.x.

Indeed.

>> We'd like to know how to crack this so we don't have to run with
>> deprecated Guile code when running with V2.
>
> I'd like to know how to detect if it's needed too, since we have
> a similar problem.

(cond-expand (guile-2 'alright)
             (guile (debug-enable 'debug)))

Thanks,
Ludo’.




  parent reply	other threads:[~2011-08-22 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 10:37 Compatibility V1.8 and 2.0 - deprecated (debug-enable 'debug) Ian Hulin
2011-08-09 12:59 ` Peter TB Brett
2011-08-09 15:12   ` Thien-Thi Nguyen
2011-08-10 18:50     ` Ian Hulin
2011-08-14  6:51       ` Thien-Thi Nguyen
2011-08-22 20:59   ` Ludovic Courtès [this message]
2012-01-09 15:20     ` Andy Wingo

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=87y5yli2mn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-user@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).