From: Andreas Rottmann <e9926584@student.tuwien.ac.at>
Cc: guile-user@gnu.org, guile-gtk-general@gnu.org
Subject: Re: New g-wrap supported in guile-gtk--rotty-0.1!
Date: 04 Dec 2003 18:21:34 +0100 [thread overview]
Message-ID: <0oswu9csdlt.fsf@pc061.ben.tuwien.ac.at> (raw)
In-Reply-To: <xy7k75cllfp.fsf@chunk.mit.edu>
Mikael Djurfeldt <mdj@mit.edu> writes:
[ First of all: Thanks for the quick answer ]
> Andreas Rottmann <a.rottmann@gmx.at> writes:
>
> > Yes, I also think that we *have* to get the "time-to-initial-window"
> > at least under 1 second for a hello world program...
>
> GOOPS is, as yet, only optimized for fast execution. Creation of
> objects and *especially* method creation involves a lot of work, most
> of which is done by interpreted Scheme code.
>
> This is not an architectural problem, though, and it is certainly
> possible to speed things up.
>
> An improvement of method addition on the algorithm level that could
> help this particular case would be to allow for adding multiple
> methods at once. Presently, every call to scm_add_method involves
> re-computing the methods list of the GF which means that adding N
> methods to a GF is O(N^2).
>
Ok, so we'd have a scm_add_methods() with this approach, I guess. I'll
have a look into this. I definitly want to have fast bindings when
Guile 1.8 comes out.
> An improvement on the implementation level would be to do part (or
> all) of the work in C. This, however, should be done with preserved
> respect for the MOP. Anyone who wants to do this should talk to me
> first.
>
Best would probably to go for algorithmic performance increase at the
SCM level first and if that doesn't suffice, factor the critical parts
out into C.
> (Unfortunately, I can't do any work on GOOPS right now. Hopefully
> I'll be able to go over a few issues with GOOPS starting next summer.)
>
I'll do a bit of code study in the next days/week, and come back to
you when I have questions, if that's OK. Once I've wrapped my head
around the code, I'll try to implement scm_add_methods() and see how
much that gains us.
--
Andreas Rottmann
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-12-04 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87smkc5b22.fsf@alice.rotty.yi.org>
[not found] ` <874qwhsa2u.fsf@zip.com.au>
2003-12-04 9:02 ` New g-wrap supported in guile-gtk--rotty-0.1! Andreas Rottmann
2003-12-04 14:14 ` Mikael Djurfeldt
2003-12-04 17:21 ` Andreas Rottmann [this message]
2003-12-04 22:33 ` Andreas Rottmann
2003-12-06 16:18 ` Andreas Rottmann
[not found] ` <1074535797.1517.64.camel@localhost>
2004-01-23 11:38 ` [GOOPS] Specializing <generic> to allow lazy method addition Andreas Rottmann
2004-01-27 15:17 ` Mikael Djurfeldt
2004-01-27 23:27 ` Stephen Compall
2004-01-28 2:14 ` Mikael Djurfeldt
2004-02-01 19:41 ` Guile warts (was: [GOOPS] Specializing <generic> to allow lazy method addition) Andy Wingo
2004-02-05 19:03 ` Guile warts Mikael Djurfeldt
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=0oswu9csdlt.fsf@pc061.ben.tuwien.ac.at \
--to=e9926584@student.tuwien.ac.at \
--cc=guile-gtk-general@gnu.org \
--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).