From: Marius Vollmer <mvo@zagadka.ping.de>
To: "Greg J. Badros" <gjb@cs.washington.edu>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: gtk-clist-append does not work with shared substrings
Date: Wed, 19 Jan 2000 11:10:00 -0000 [thread overview]
Message-ID: <87snzt6frz.fsf@zagadka.ping.de> (raw)
In-Reply-To: <qrr901pehav.fsf@clavicle.cs.washington.edu>
"Greg J. Badros" <gjb@cs.washington.edu> writes:
> Whereas this works:
> ;; (gtk-clist-append clist (list "foo" "bar"))
>
> This does not:
>
> ;; (gtk-clist-append clist (list (make-shared-substring "foo") "bar"))
Hmm, I get:
guile> (use-modules (gtk gtk))
guile> (define clist (gtk-clist-new 2))
guile> (gtk-clist-append clist (list "foo" "bar"))
0
guile> (gtk-clist-append clist (list (make-shared-substring "foo") "bar"))
1
guile>
Maybe I'm using the wrong Guile version. Shared substrings should be
converted to normal strings via the `sgtk_string_conversion' function.
It has this definition:
SCM
sgtk_string_conversion (SCM str)
{
if (SCM_NIMP (str) && SCM_STRINGP (str))
SCM_COERCE_SUBSTR (str);
return str;
}
There is likely something wrong with the way conversions are handled
for composite types, like the list you are using.
> Also, I don't think there's any way to tell which version of guile-gtk
> you're linked against. `guile-gtk-version' is a nice primitive to add.
There is the (gtk config) module which contains config information.
It even has a `gtkconf-version' entry but that reflects the version of
Gtk+ that this guile-gtk is build for. I think we should change that
to be the guile-gtk version and add explicit support for the Gtk+
version in use. This should come from (gtk dynlink) as that module
knows which library has been dynlinked (guile-gtk-1.2 or
guile-gtk-1.3). Ariel?
next prev parent reply other threads:[~2000-01-19 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-16 15:19 Greg J. Badros
2000-01-19 11:10 ` Marius Vollmer [this message]
2000-01-19 11:37 ` Greg J. Badros
2000-01-20 22:13 ` Marius Vollmer
2000-01-20 21:22 ` Greg J. Badros
2000-01-23 8:04 ` Marius Vollmer
2000-01-23 9:26 ` Greg J. Badros
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=87snzt6frz.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=gjb@cs.washington.edu \
--cc=guile-gtk@sourceware.cygnus.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).