caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: ijtrotts@ucdavis.edu, caml-list@inria.fr
Subject: Re: [Caml-list] OpenGL
Date: Thu, 8 Apr 2004 17:37:52 +0100	[thread overview]
Message-ID: <20040408163752.GA4315@quick.recoil.org> (raw)
In-Reply-To: <20040407160739.GB13223@mev>

On Wed, Apr 07, 2004 at 09:07:39AM -0700, Issac Trotts wrote:
> On Thu, Apr 08, 2004 at 04:11:25PM +0100, Jon Harrop wrote:
> > 
> > On Thursday 08 April 2004 3:53 pm, John Goerzen wrote:
> > > I'm just saying that I think that
> > > "Ocaml has a robust set of tools for real-world uses" is inaccurate.
> > 
> > Yes, I agree. Personally, I would like to see a carefully thought out 
> > interface to OpenGL, GLU etc. They are very stable and mature libraries which 
> > were superbly thought out but, unfortunately, suffer from a low-level API 
> > which sometimes ends up in a lot of "void *" raw data getting passed around 
> > and kept. I do not know of an existing, elegant interface to these libraries 
> > in any functional language and, IMHO, it would be a big but very worthwhile 
> > undertaking to create such an interface. I think this would make a good PhD 
> > for someone...
> 
> Did you look at LablGL?

LablGL provides an almost 1-1 mapping between the C and OCaml OpenGL
calls... it works really well when working with the simpler bits of
OpenGL, but it rapidly descends into using a bunch of raw types for
things like the GLU tessellator.

Still, Ocaml/LablGL is a great combination for me so far - drawing
individual scene elements functionally, and rendering them with
'imperative glue' seems a natural fit for Ocaml.

-- 
Anil Madhavapeddy                                 http://anil.recoil.org
University of Cambridge                          http://www.cl.cam.ac.uk

-------------------
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


      parent reply	other threads:[~2004-04-08 16:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 15:11 Jon Harrop
2004-04-07 16:07 ` Issac Trotts
2004-04-08 16:35   ` Jon Harrop
2004-04-08 20:19     ` Issac Trotts
2004-04-08 20:46       ` [Caml-list] Re: Triangle (was: OpenGL) Christophe TROESTLER
2004-04-08 22:25       ` [Caml-list] OpenGL Jon Harrop
2004-04-09  1:45         ` Brian Hurt
2004-04-09  2:57           ` Brandon J. Van Every
2004-04-09 10:57           ` Jon Harrop
2004-04-09 16:12             ` Brian Hurt
2004-04-10  4:32               ` Brandon J. Van Every
2004-04-10  4:59                 ` Kenneth Knowles
2004-04-10  8:17                 ` Nicolas Cannasse
2004-04-11  6:20                 ` Brian Hurt
2004-04-11  8:10                   ` skaller
2004-04-11  9:23                   ` Brandon J. Van Every
2004-04-11 12:08                     ` Jon Harrop
2004-04-11 12:01                   ` Jon Harrop
2004-04-09 12:52         ` Issac Trotts
2004-04-08 16:37   ` Anil Madhavapeddy [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040408163752.GA4315@quick.recoil.org \
    --to=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=ijtrotts@ucdavis.edu \
    /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).