From: "Anton N. Mescheryakov" <targon@ihed.ras.ru>
Subject: guile usage in prototype 3d engine
Date: Mon, 11 Nov 2002 14:26:29 +0300 [thread overview]
Message-ID: <3DCF93E5.1010300@ihed.ras.ru> (raw)
Dear schemers,
One may say I'am bizzare, but I try to make 3D engine embedded into
Guile system. Such kind of program needs high degree of modularity,
extensibility and wise configuration, while modern HW T&L cards can
deliver vast FPS despite CPU's ugly mess (like scripting engine in main
loop:). So I would be pleased to read some success/horror stories
concerning similar guile projects etc.
Another thing: is it OK to use u-vectors as 3D/4D coordinates, or I need
to introduce special smobs, or simply use lists? Many aspects of guile
are, er, not especialy well documented, including array access.
With best regards,
Anton.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2002-11-11 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 11:26 Anton N. Mescheryakov [this message]
2002-11-12 8:47 ` guile usage in prototype 3d engine Thien-Thi Nguyen
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=3DCF93E5.1010300@ihed.ras.ru \
--to=targon@ihed.ras.ru \
/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).