|
|
||
|
|
Start of topic | Skip to actions
The Monty Project FFI TaskOwners: Blake Kaplan, Peter Hokanson.Goal: To create a foreign function interface to allow OCaml to access and execute Python libraries written in C Extending the OCaml interface to Python/C API (11/09/2007)Goal time for completion: Sat Nov 10, noon. Pete and Blake will extend the OCaml interface to the Python/C API. The following API interface functions will be implemented (click on links to see the actual Python/C API documentation of the functions):
As Pete and Blake add these functions, they will be adding a list of each function implemented correctly to the wiki. If they leave an API function or have problems implementing it, that will be on the wiki. TODO (11/05/2007)We are still in the design phase, and we believe that the following steps may help getting started.
DiscussionI looked briefly at the Python/C API documentation yesterday and outside of the type declarations that it provides, it doesn't look like it's going to be useful for our FFI implementation. I met up with Raj today after the meeting and we talked briefly about exactly what problems we need to solve. So far our talks have been focusing on FFI+libraries. I think that reformulating the problem as being "introduce an FFI for Monty" and separately "implement Python libraries" will give us better separation and allow us to wrap our heads around the various problems more easily. -- BlakeKaplan - 07 Nov 2007 Useful links
The Man Behind the Curtain
Topic Actions: Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r20 < r19 < r18 < r17 < r16 | More topic actions
Webs: Main | TWiki | Africa | EmbeddedSystems | Gpce | Houston | International | K12 | MetaOCaml | MulticoreOCR | ProgrammingLanguages | RAP | RIDL | Sandbox | SpeechClub | Teaching | Texbot | WG211 Web Actions:
RAP.TaskMontyFFI moved from RAP.TaskForeignFunctionInterface on 06 Nov 2007 - 23:43 by Main.WalidTaha - put it back
|
|
This work is licensed under a Creative Commons Attribution 2.5 License. Please follow our citation guidelines.