From: Thien-Thi Nguyen <ttn@surf.glug.org>
Cc: guile-user@gnu.org
Subject: Re: guile-sdl vs Projector
Date: Mon, 16 Feb 2004 07:01:52 +0100 [thread overview]
Message-ID: <E1AsbpI-0005Rd-00@surf.glug.org> (raw)
In-Reply-To: <16431.58886.346893.634019@gargle.gargle.HOWL> (510046470588-0001@t-online.de)
From: 510046470588-0001@t-online.de (klaus schilling)
Date: Sun, 15 Feb 2004 22:35:02 +0100
what is the difference between Projector and guile-sdl ?
projector is no longer maintained. the projector author contributed
code to guile-sdl, which then also went through a period of neglect
before finding new maintainership.
projector installation is a shared object library in ${libdir} (if i
recall correctly -- i played w/ it from the build dir w/o installing).
guile-sdl installation are compiled modules in ${libdir}/guile/site/sdl
(compiled modules are shared object libraries that follow certain
conventions).
projector has fewer smob types (and hence less type checking) than
guile-sdl. consequently projector is a bit faster and less memory-using
than guile-sdl but crashes more easily on uncareful code.
projector uses variables in most places where guile-sdl uses symbols
(event codes, keysyms, etc).
projector proc names begin with "sdl-" (usually, there are some
exceptions) while guile-sdl leaves prefixing to the user.
projector does not support ttf.
these are the things i can think of pre-coffee. i have spiffed this
list and placed it on the guile-sdl home page. updates from those w/
better memory (or more blood-bound caffeine) welcome.
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2004-02-16 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 21:35 guile-sdl vs Projector klaus schilling
2004-02-16 6:01 ` Thien-Thi Nguyen [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
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=E1AsbpI-0005Rd-00@surf.glug.org \
--to=ttn@surf.glug.org \
--cc=guile-user@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).