From: Andreas Rottmann <a.rottmann@gmx.at>
To: guile-gtk@sources.redhat.com
Subject: Re: guile-gobject problem
Date: Fri, 15 Aug 2003 13:58:00 -0000 [thread overview]
Message-ID: <87n0eb3tvr.fsf@alice.rotty.yi.org> (raw)
In-Reply-To: <20030815130928.GA926@lark> (Andy Wingo's message of "Fri, 15 Aug 2003 14:09:28 +0100")
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
Andy Wingo <wingo@pobox.com> writes:
> There've been some internet difficulties at my workplace, but hopefully
> they're sorted out now...
>
> On Mon, 11 Aug 2003, Andreas Rottmann wrote:
>
>> | DSTWService* <dstwservice*>
>> | gboolean <gboolean>
>> | GType <gtype>
>> | char* <char*>
>> | none <none>
>> | gunichar* <gunichar*>
>
> Hmm, looks like you forgot to set the standard wrapset as a used
> wrapset. Check the gw-atk-spec.scm for more details, bit it will suffice
> to add (gw:wrapset-depends-on ws "guile-gnome-gw-standard") to your
> wrapset definition code.
>
> Of course, you have to also depend on glib and gobject if you want those
> types to be recognized as well.
>
I posted the wrng .spec version, I had those depends in place. In fact
this is a bug in defs-support.scm; the function doesn't search in the
depended-on wrapsets if there are no types registered or the
wrapset. The attached patch should fix this.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: find-recursive.patch --]
[-- Type: text/x-patch, Size: 1610 bytes --]
Index: gnome/gobject/defs-support.scm
===================================================================
RCS file: /cvsroot/guile-gtk/guile-gobject/gnome/gobject/defs-support.scm,v
retrieving revision 1.3
diff -u -p -r1.3 defs-support.scm
--- gnome/gobject/defs-support.scm 1 Jul 2003 16:10:25 -0000 1.3
+++ gnome/gobject/defs-support.scm 15 Aug 2003 13:46:59 -0000
@@ -34,20 +34,20 @@
(define (recursive-type-find ws type)
(let* ((ws-name (gw:wrapset-get-name ws))
(types-hash (hash-ref types-hash-hash ws-name)))
- (if types-hash
- (let ((ret (hash-ref types-hash type)))
- (if ret
- ret
- (call-with-current-continuation
- (lambda (exit)
- (for-each
- (lambda (ws)
- (let ((ret (recursive-type-find ws type)))
- (if ret
- (exit ret))))
- (wrapset-get-wrapsets-depended-on ws))
- #f))))
- #f)))
+ (let ((ret (if types-hash
+ (hash-ref types-hash type)
+ #f)))
+ (if ret
+ ret
+ (call-with-current-continuation
+ (lambda (exit)
+ (for-each
+ (lambda (ws)
+ (let ((ret (recursive-type-find ws type)))
+ (if ret
+ (exit ret))))
+ (wrapset-get-wrapsets-depended-on ws))
+ #f))))))
;; find the gwrap type name for a given type name in a defs file, or
;; wrap the type as an opaque gpointer -- this thing is getting nasty!
[-- Attachment #3: Type: text/plain, Size: 276 bytes --]
Regards, Andy
--
Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | a.rottmann@gmx.at
http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
Make free software, not war!
prev parent reply other threads:[~2003-08-15 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 20:30 Andreas Rottmann
2003-08-12 14:49 ` guile-gobject problem [solved], g-wrap Andreas Rottmann
2003-08-12 15:29 ` Greg Troxel
2003-08-12 16:31 ` Andreas Rottmann
2003-08-12 17:00 ` Rob Browning
2003-08-15 13:19 ` guile-gobject problem Andy Wingo
2003-08-15 13:58 ` Andreas Rottmann [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87n0eb3tvr.fsf@alice.rotty.yi.org \
--to=a.rottmann@gmx.at \
--cc=guile-gtk@sources.redhat.com \
/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).