unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Ian Hulin <ian@hulin.org.uk>
Cc: guile-user@gnu.org
Subject: Re: Compatibility V1.8 and 2.0 - deprecated (debug-enable 'debug)
Date: Sun, 14 Aug 2011 08:51:11 +0200	[thread overview]
Message-ID: <87mxfch4f4.fsf@ambire.localdomain> (raw)
In-Reply-To: <j1ujtc$vee$1@dough.gmane.org> (Ian Hulin's message of "Wed, 10 Aug 2011 19:50:23 +0100")

() Ian Hulin <ian@hulin.org.uk>
() Wed, 10 Aug 2011 19:50:23 +0100

   Thanks for the info, it would be useful but we need to things at
   run-time.  We've got stuff in an initialization scheme script which is
   called from the Lilypond code image and this historically has done the
   (debug-enable 'debug) call.

Another idea is to move these small pieces into separate files
and conditionally load them...

   I want to be able to code it for backwards-compatibility for Guile V2 and
   Guile V1.8, and also not cause any deprecation warnings when running with
   Guile V2.  E.g.

   ;;; Boolean thunk - are we integrating Guile V2.0 or higher with Lily?
   (define-public (guile-v2)
     (string>? (version) "1.9.10"))

... based on ‘guile-v2’ (for example).  This might be enough to keep
the deprecation warnings from appearing.  I don't know for sure, however.



  reply	other threads:[~2011-08-14  6:51 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 [this message]
2011-08-22 20:59   ` Ludovic Courtès
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=87mxfch4f4.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=guile-user@gnu.org \
    --cc=ian@hulin.org.uk \
    /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).