From: Richard Shann <richard.shann@virgin.net>
To: guile-user@gnu.org
Subject: More Guile 1.8 code failing in 2.x
Date: Wed, 27 Feb 2013 10:07:23 +0000 [thread overview]
Message-ID: <1361959643.2097.179.camel@debian-box.lan> (raw)
We have one more construct being refused as we upgrade to guile 2.0 in
GNU/Denemo
(if (not (defined? 'ToggleTripleting::InsideTriplet))
(define ToggleTripleting::InsideTriplet #t))
It is intended to set up a flag which toggles between true and false on
each call. If already set up, the flag is not altered.
Apparently (I haven't been able to check) Guile 2.0 gives an error.
#f definition in expression context, where definitions are not allowed, ((line . 2) (column . 4) (filename . #f)) (define ToggleTripleting::InsideTriplet #t) #f)
Can anyone suggest what could replace that? I would prefer to to replace
it with something that has the same semantics, rather than setting up
some alternative method of handling the situation - registering all such
variables on program startup, or some such - as at the moment this code
only evaluated if used and doesn't require any mechanism to get
initialized, other than this construct.
Richard Shann
next reply other threads:[~2013-02-27 10:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 10:07 Richard Shann [this message]
2013-02-27 13:19 ` More Guile 1.8 code failing in 2.x mark
2013-02-27 14:22 ` Richard Shann
2013-02-27 14:28 ` Ludovic Courtès
2013-02-27 14:48 ` Mike Gran
2013-02-27 17:54 ` Richard Shann
2013-02-27 15:08 ` Andy Wingo
2013-02-27 15:13 ` Andy Wingo
2013-02-27 17:59 ` Richard Shann
2013-02-27 14:50 ` Stefan Israelsson Tampe
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=1361959643.2097.179.camel@debian-box.lan \
--to=richard.shann@virgin.net \
--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).