Pretty straightforward. Edit call_types.txt. First parameter's the
return type, the rest are the parameter types. Use "p" for any
generic "i've stuffed a struct pointer into a PMC" type. Do please
only add in signatures for functions you're actually going to call
(or are adding if you're adding in a full library) as we'd rather not
have nci.o get *too* big...
If I've got things set properly, nci.c should get rebuilt if either
call_types.txt or build_nativecall.pl change, but do feel free to add
in other checks, just to make sure. I'd hate to have too much stale
stuff hanging around.
Also, at the moment I can't test this. (The dynaloading on Darwin
only works on .bundle files not .dylib files (I think I know how to
fix this), and my linux box's headers are all screwed up somehow) So
if someone wants to pick a target library and try it out, well,
that'd be fine with me.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
- Re: Adding new function signatures to parrot's NCI call lis... Dan Sugalski
- Re: Adding new function signatures to parrot's NCI cal... James Mastros
- Re: Adding new function signatures to parrot's NCI... James Mastros
- Re: Adding new function signatures to parrot's NCI cal... Leon Brocard
- Re: Adding new function signatures to parrot's NCI... Gopal V
- Re: Adding new function signatures to parrot's NCI... Dan Sugalski
- Re: Adding new function signatures to parrot's... Leon Brocard
- Curses Life Leon Brocard
- Re: Curses Life Dan Sugalski
- Re: Curses Life Piers Cawley
- Re: Curses Life Nicholas Clark