Here is the idea:
For version v3.0.0
Using Parrot and the compiler tools, write a parser for C header files
that can generate Perl 5 NCI or Parrot NCI code.
It should let the developer write an SDL binding for either language
by running the parser against SDL.h and its friends. For output, it
would generate either or both Perl 5 and Parrot code that:
* opens the appropriate library with NCI or Parrot NCI
* binds to the functions with the appropriate data types
* declares the defined structs appropriately
Developers should be able to include this generated code in the
distribution so that end users never have to run this compiler tools
themselves or even have the headers for the libraries installed.
Obviously they need the NCI and bound libraries installed, but not the
headers or even a C compiler.
Lifted from http://www.perl.org/advocacy/summerofcode/ideas.html
On Aug 5, 4:18 pm, ge...@broadwell.org (Geoffrey Broadwell) wrote:
> On Wed, 2009-08-05 at 15:06 -0400, Kartik Thakore wrote:
> > Awesome! A few things. A new cpan distro is going to appear. Moreover
> > we have a roadmap plan now and on of the things on it are a parrot
> > parser so that users will not have to compile sdl bindings and our
> > work will carry over into perl6.
>
> OK, you guys had my attention before, but now it's really focused. What
> do you mean by "a parrot parser"? Are you planning to rewrite the
> existing Parrot SDL bindings?
More likely we will steal, beg, borrow and merge!
> (For reference, I maintain the Parrot OpenGL bindings; chromatic was I
> believe the last Parrot SDL maintainer, but the Parrot SDL bindings have
> bitrotted somewhat since he's been focused on the Parrot core.)
I noticed that.
> If you want to get in touch with us out in Parrot land, we'd be happy to
> help! I suggest #parrot on irc.perl.org and the parrot-dev mailing
> list; details at:
>
> http://www.parrot.org/dev
>
> -'f
Thanks.
