I think that's pretty accurate. I do a relatively large amount of GL programming and our library does not cover very much of it at all. My personal opinion is that it is better invest time in to good FFI generation tools (parsing C headers and interactively generating an API), then brute-force generation of FFIs for each thing. I've written a lot of FFIs and I'm seeing lots of common tools that I think could be abstracted. That said, if someone else (Stephan, for example) were to improve manual bindings we have, I would take responsibility for maintaining and testing it in the future.
Jay 2011/4/8 John Clements <cleme...@brinckerhoff.org>: > > On Apr 8, 2011, at 11:43 AM, Stephan Houben wrote: > >> Hi list, >> >> As described in the documentation, the OpenGL support >> in Racket does not include the vertex array API >> (glVertexPointer etc.). >> >> Can I ask why this is? >> I noticed in gl.rkt that it is present but outcommented, so >> I suppose the reason is not lack of time but rather that >> it didn't work on some/all platforms. > > Let me preface my comment by saying that this is secondhand knowledge. > > One of my students informed me about a month ago that our OpenGL interface is > hideously out of date. "It doesn't even support version 2", he said. My > guess--and it's just a guess--is that what you're seeing *is* due to a lack > of the time and energy required to update the FFI. > > Feel like doing it? > > All the best, > > John Clements > > > _________________________________________________ > For list-related administrative tasks: > http://lists.racket-lang.org/listinfo/users > -- Jay McCarthy <j...@cs.byu.edu> Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93 _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
