From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: More Guile 1.8 code failing in 2.x
Date: Wed, 27 Feb 2013 15:28:32 +0100 [thread overview]
Message-ID: <87zjypx23z.fsf@gnu.org> (raw)
In-Reply-To: 1361974971.2097.194.camel@debian-box.lan
Richard Shann <richard.shann@virgin.net> skribis:
> (if (defined? 'define-once)
> (define-once ToggleTripleting::InsideTriplet #t)
> (eval-string "(if (not (defined? 'ToggleTripleting::InsideTriplet))
> (define ToggleTripleting::InsideTriplet #t))"))
Rather something along these lines:
(cond-expand ((not guile-2)
(define-macro (define-once var expr)
`(if (not (defined? ',var))
(define ,var ,expr))))
(guile-2 #t))
This will do nothing on Guile 2.0, and will define ‘define-once’ on 1.8.
HTH,
Ludo’.
next prev parent reply other threads:[~2013-02-27 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 10:07 More Guile 1.8 code failing in 2.x Richard Shann
2013-02-27 13:19 ` mark
2013-02-27 14:22 ` Richard Shann
2013-02-27 14:28 ` Ludovic Courtès [this message]
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=87zjypx23z.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).