From: Greg Troxel <gdt@ir.bbn.com>
To: Andreas Rottmann <a.rottmann@gmx.at>
Cc: guile-gtk@sources.redhat.com, rlb@defaultvalue.org
Subject: Re: guile-gobject problem [solved], g-wrap
Date: Tue, 12 Aug 2003 15:29:00 -0000 [thread overview]
Message-ID: <rmik79isxli.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87vft353sc.fsf@alice.rotty.yi.org>
[I fixed the spelling of Rob's username - it was rbl in your mail.]
I've found & fixed the bug. I'll commit to CVS (just have been given
access by Marius!), after posting a patch here for review. First,
however, I'd like to discuss (once again ;-)), the forking of
g-wrap. I could check in a g-wrap into the guile-gtk CVS repository
that provides:
* Argument hiding (needed for GError exceptions).
* An argument call-ccg (needed for GError, since it is passed
by double-refernce (pointer to pointer)).
* A changed (generating less code) mechanism to
wrap enums (this only has gains for non-GObject enums, though).
* The patched gw-standard-spec.scm as provided by guile-gobject today.
* An exported gw:wrapset-get-wrapsets-depended-on (the fix
mentioned already uses this, although it could be changed not
to use it easily).
Not that I know what's really up, but note that gnucash is said to be
short of developer cycles. So creating a g-wrap _project_ on
savannah, rather than putting it under guile-gtk, and trying to make
sure (a bit) it still works for other uses, and perhaps a release,
might be a real contribution.
--
Greg Troxel <gdt@ir.bbn.com>
next prev parent reply other threads:[~2003-08-12 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 20:30 guile-gobject problem Andreas Rottmann
2003-08-12 14:49 ` guile-gobject problem [solved], g-wrap Andreas Rottmann
2003-08-12 15:29 ` Greg Troxel [this message]
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
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=rmik79isxli.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=a.rottmann@gmx.at \
--cc=guile-gtk@sources.redhat.com \
--cc=rlb@defaultvalue.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).