Portable OpenGL via Parrot - was: Extending Parrot NCI callback functionality Options

2008-03-27 Thread Bob Free
;Grafman" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, March 26, 2008 3:44 PM Subject: Re: Extending Parrot NCI callback functionality Options On Wed, 2008-03-26 at 09:31 -0700, Grafman wrote: He lives! Just kidding, I know you'v

Re: Portable OpenGL via Parrot - was: Extending Parrot NCI callback functionality Options

2008-03-26 Thread Geoffrey Broadwell
On Wed, 2008-03-26 at 16:27 -0700, Bob Free wrote: > Cool - great to hear from you - sorry that it's been a while since I've > posted an update! Real life can be so darned intrusive ;-) > It'd be great to have you participate - you've done quite a lot for POGL. > Regarding your work/ideas

Re: Extending Parrot NCI callback functionality Options

2008-03-26 Thread Arcady Goldmints-Orlov
As far as I understand OpenGL, it's got one current context per thread, and libGL does all sorts of evil things with threads and thread-local storage to make it all work transparently. An object-oriented OpenGL interface seems like the right way to go, though, for all sorts of other reasons. Arcad

Re: Extending Parrot NCI callback functionality Options

2008-03-26 Thread Geoffrey Broadwell
On Wed, 2008-03-26 at 09:31 -0700, Grafman wrote: He lives! Just kidding, I know you've had actual paid work going on. :-) > Hi chromatic - as you know, I took over the Perl OpenGL project over a > year ago - you had mentioned that I might consider doing a port to > Parrot; Geoffrey had suggest

Extending Parrot NCI callback functionality Options

2008-03-26 Thread Grafman
> I'm not even sure *that* will work. To invoke a Sub PMC from C, you > need to pass in an Interp as well as the PMC. Unless you know both > of those at compile time, I'm not sure how to make the callback > mechanism work. > > ... although I just had an evil idea regarding memcpy and a hash table