Compatibility V1.8 and 2.0 - deprecated (debug-enable 'debug)

Compatibility V1.8 and 2.0 - deprecated (debug-enable 'debug)

[Ian Hulin]

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.

We'd like to know how to crack this so we don't have to run with
deprecated Guile code when running with V2.

Cheers,
Ian Hulin

Re: Compatibility V1.8 and 2.0 - deprecated (debug-enable 'debug)

[Peter TB Brett]

[-- Attachment #1: Type: text/plain, Size: 702 bytes --]

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.

> 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.

                              Peter


-- 
Peter Brett <peter@peter-b.co.uk>
Remote Sensing Research Group
Surrey Space Centre

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: Compatibility V1.8 and 2.0 - deprecated (debug-enable 'debug)

[Thien-Thi Nguyen]

() Peter TB Brett <peter@peter-b.co.uk>
() Tue, 09 Aug 2011 13:59:50 +0100

   I'd like to know how to detect if it's needed too, since we
   have a similar problem.

One way is to run a check in configure.ac.  In the ttn-do slog
(portability futzing effort) from Guile 1.4.x-only to a wider world,
there is the file baux/snuggle.m4, which can be used, e.g.,:

  AC_CACHE_CHECK([whether Guile accepts (debug-enable 'debug)],
    [guile_cv_ded],
    [SNUGGLE_CHECK([guile_cv_ded],[(debug-enable 'debug)])])
  
  AS_IF([test xyes = x"$guile_cv_ded"],
    ARRANGE-TO-KEEP-USING-IT,
    ARRANGE-TO-OMIT-IT)

The ttn-do configure.ac has other examples.  See:

  http://www.gnuvola.org/software/ttn-do/

BTW, snuggle.m4 is from the SNUGGLE project: "SNUGGLE:
Neutralize Uncharacteristically Grotesque GUILE Library Entropy!"

Re: Compatibility V1.8 and 2.0 - deprecated (debug-enable 'debug)

[Ian Hulin]

Hi Thien-Thi,
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.  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"))
.
.
.
(if (not (guile-v2))
  (debug-enable 'debug) ;; Guile V1.8.7
  (begin        	;; Guile V2 options
    (debug-enable 'backtrace)
    (debug-enable 'show-file-name)))

Is there anything I can code when running with Guile V2 that provides
the equivalent functionality to (debug-enable 'debug), but will not
trigger deprecation warnings, or will this:

(if (not (guile-v2))
  (debug-enable 'debug)) ;; Guile V1.8.7

be all I can do?

Cheers,

Ian Hulin

Re: Compatibility V1.8 and 2.0 - deprecated (debug-enable 'debug)

[Thien-Thi Nguyen]

() 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.

Re: Compatibility V1.8 and 2.0 - deprecated (debug-enable 'debug)

[Ludovic Courtès]

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’.

Re: Compatibility V1.8 and 2.0 - deprecated (debug-enable 'debug)

[Andy Wingo]

On Mon 22 Aug 2011 22:59, ludo@gnu.org (Ludovic Courtès) writes:

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

Or:

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

Regards,

Andy
-- 
http://wingolog.org/