From: Brian Hurt <bhurt@spnz.org>
To: caml <caml-list@inria.fr>
Cc: ExtLib <ocaml-lib-devel@lists.sourceforge.net>
Subject: [Caml-list] RE: 3D Rendering pipeline
Date: Tue, 8 Jun 2004 21:57:11 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0406082148400.4243-100000@localhost.localdomain> (raw)
In-Reply-To: <OOEALCJCKEBJBIJHCNJDKEFJHDAB.vanevery@indiegamedesign.com>
Ignoring the flamefest for a bit, I actually have a question for people
who do 3D rendering pipelines. Over in Extlib (plug:
http://sourceforge.net/projects/ocaml-lib/) we have "enumerators"-
basically Java or C++ STL Iterators. Except that we have lazy mapping and
filters- basically, as each element is iterated, all the currently
applicable maps and filters are applied to it.
So my question is: would this be a better paradigm to experiment with a
graphics pipeline in? What other tweaks or features might make it more
usefull?
--
"Usenet is like a herd of performing elephants with diarrhea -- massive,
difficult to redirect, awe-inspiring, entertaining, and a source of
mind-boggling amounts of excrement when you least expect it."
- Gene Spafford
Brian
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-06-09 2:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 11:13 [Caml-list] 32 bit floats, SSE instructions Brandon J. Van Every
2004-06-07 11:32 ` Christophe TROESTLER
[not found] ` <20040607131717.GA12136@gaia.cc.gatech.edu>
2004-06-07 16:53 ` Christophe TROESTLER
2004-06-07 19:30 ` Brandon J. Van Every
2004-06-07 20:39 ` Nicolas Cannasse
2004-06-08 5:42 ` Brandon J. Van Every
2004-06-08 16:54 ` Jon Harrop
2004-06-08 20:50 ` Brandon J. Van Every
2004-06-09 3:19 ` skaller
2004-06-08 14:23 ` Keith Wansbrough
2004-06-10 14:43 ` David Brown
2004-06-10 15:20 ` Keith Wansbrough
2004-06-10 15:57 ` skaller
2004-06-10 16:23 ` Keith Wansbrough
2004-06-10 16:47 ` skaller
2004-06-10 19:46 ` Evan Martin
2004-06-07 21:00 ` Richard Jones
2004-06-07 21:42 ` Jon Harrop
2004-06-09 15:55 ` Richard Jones
2004-06-07 22:48 ` Chris Clearwater
2004-06-07 17:01 ` brogoff
2004-06-08 1:50 ` Brian Hurt
2004-06-08 5:27 ` Brandon J. Van Every
2004-06-08 15:05 ` Brian Hurt
2004-06-08 16:50 ` art yerkes
2004-06-08 17:10 ` Jon Harrop
2004-06-08 19:24 ` Brandon J. Van Every
2004-06-09 0:25 ` Jon Harrop
2004-06-09 1:28 ` [Caml-list] 3D graphics debate Brandon J. Van Every
2004-06-09 2:40 ` Jon Harrop
2004-06-09 8:09 ` Brandon J. Van Every
2004-06-09 1:33 ` [Caml-list] 32 bit floats, SSE instructions Brandon J. Van Every
2004-06-09 3:04 ` Jon Harrop
2004-06-09 8:33 ` [Caml-list] The multiresolution business model Brandon J. Van Every
2004-06-09 3:27 ` [Caml-list] 32 bit floats, SSE instructions skaller
2004-06-09 14:21 ` Christophe TROESTLER
2004-06-09 2:57 ` Brian Hurt [this message]
2004-06-10 17:55 ` [Caml-list] Re: [Ocaml-lib-devel] RE: 3D Rendering pipeline Nicolas Cannasse
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=Pine.LNX.4.44.0406082148400.4243-100000@localhost.localdomain \
--to=bhurt@spnz.org \
--cc=caml-list@inria.fr \
--cc=ocaml-lib-devel@lists.sourceforge.net \
/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 NNTP newsgroup(s).