From: Peter TB Brett <peter@peter-b.co.uk>
To: guile-user@gnu.org
Subject: gEDA now supports Guile 2.0! (And an issue).
Date: Sat, 04 Jun 2011 01:26:11 +0100 [thread overview]
Message-ID: <m3vcwme924.fsf@harrington.peter-b.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
Hi folks,
I just finished porting gEDA (http://www.gpleda.org/) to Guile 2.0!
I encountered one problem, though.
In Guile 1.8.x, scm_display_error() takes a stack as the first
argument. In Guile 2.0.x, scm_display_error() takes a frame as the
first argument.
Can anyone suggest a sensible way to support both? I haven't been able
to figure out a good feature test... at the moment I've had to resort to
passing #f. :-(
Peter
--
Peter Brett <peter@peter-b.co.uk>
Remote Sensing Research Group
Surrey Space Centre
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2011-06-04 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 0:26 Peter TB Brett [this message]
2011-06-04 2:59 ` gEDA now supports Guile 2.0! (And an issue) nalaginrut
2011-06-04 8:42 ` Neil Jerram
2012-01-08 15:38 ` 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=m3vcwme924.fsf@harrington.peter-b.co.uk \
--to=peter@peter-b.co.uk \
--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).