As a developer of the glue code, you'll need to have intimate knowledge of the function signatures and data structures contained within the header file (assuming you're gluing some existing C library to perl). But once the glue is developed, you won't need the header file at all because all of the info will be in the parrot source file or the perl6 module. In other words the C header file becomes a perl and/or parrot source file. Writing in perl for extensions is a whole heck of a lot easier than writing some in perl, some in C and requiring a C compiler.
| [reply] |
| [reply] |
Sounds an aweful lot like Win32::API::Prototype.
Paste the C function prototype, and the name of the dll and it returns a coderef that you call from perl using perl variables for the parameters.
Examine what is said, not who speaks.
Silence betokens consent.
Love the truth but pardon error.
| [reply] |