From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org, ariel@arcavia.com
Subject: Re: gnome-guile broken with guile 1.5 (gg used guile-snarf).
Date: Tue, 12 Mar 2002 13:04:44 -0800 [thread overview]
Message-ID: <E16ktRs-0006Xo-00@giblet> (raw)
In-Reply-To: <876641lm2g.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Tue, 12 Mar 2002 11:42:31 -0600)
From: Rob Browning <rlb@defaultvalue.org>
Date: Tue, 12 Mar 2002 11:42:31 -0600
"Drift" seems possible and even perhaps likely to me when a
particular feature that was previously undocumented, and not covered
by make check, is both publically available and used. [...] something
we're interested in trying to avoid in the future.
does anyone mind if i add this explanation to the manual in the
terminology section? it seems to be a fundamental part of the
user/maintainer dialogue.
> i suppose what i'll do is port 1.4 functionality into 1.6, add
> "--compat=1.4" (or whatever, i'm open to suggestions) option
> handling, and document these things. :-/
[with good transition docs,] I'd be happy to fix what's needed in
gnome-guile, and I suspect that Dale would be amenable to adapting
his code too, once the requirements are clear.
the transition docs and modified guile-snarf are done (testing at the
moment, checkin today likely). i will also outline the t.docs in NEWS,
and use my new vocab. hopefully compat mode can accomodate those who
aren't ready to change their source.
guile-snarf [invocation and result]
At first glance I had presumed that the problem was that although
guile-gtk.c #includes guile-gtk.x, the old snarfing process supressed
that include, but the new one doesn't, but that was just a guess.
Here's what guile-gtk.c says wrt guile-gtk.x:
#ifndef SCM_MAGIC_SNARFER
#ifndef MKDEP
#include "guile-gtk.x"
#endif /* MKDEP */
#endif /* SCM_MAGIC_SNARFER */
ack, i had been looking at how guile-1.4 does its own snarfing for a
hint at how guile-1.4 guile-snarf works, but that was a mistake!
guile-1.4 uses some other method of snarfing for itself. guile-snarf is
not even used there. must. fight. gumption. leak...
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-12 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87hentznk5.fsf@raven.i.defaultvalue.org>
[not found] ` <E16j55b-00007K-00@giblet>
[not found] ` <E16jSR5-0001VP-00@giblet>
[not found] ` <877kojuij8.fsf@raven.i.defaultvalue.org>
[not found] ` <E16ken0-0005k4-00@giblet>
2002-03-12 17:42 ` gnome-guile broken with guile 1.5 (gg used guile-snarf) Rob Browning
2002-03-12 21:04 ` Thien-Thi Nguyen [this message]
2002-03-12 21:30 ` Rob Browning
[not found] ` <E16j6cK-0000Ew-00@giblet>
[not found] ` <m366479r85.fsf@laruns.ossau.uklinux.net>
2002-03-14 2:37 ` Thien-Thi Nguyen
2002-03-14 20:34 ` Neil Jerram
2002-04-03 2:58 ` Thien-Thi Nguyen
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=E16ktRs-0006Xo-00@giblet \
--to=ttn@giblet.glug.org \
--cc=ariel@arcavia.com \
--cc=guile-devel@gnu.org \
--cc=ttn@glug.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).