[pypy-svn] r49810 - pypy/extradoc/planning/roadmap
fijal at codespeak.net
fijal at codespeak.net
Fri Dec 14 21:41:36 CET 2007
Author: fijal
Date: Fri Dec 14 21:41:34 2007
New Revision: 49810
Added:
pypy/extradoc/planning/roadmap/task_ctypes.txt (contents, props changed)
Modified:
pypy/extradoc/planning/roadmap/task_wrapper_generator.txt
Log:
Add a separate ctypes task
Added: pypy/extradoc/planning/roadmap/task_ctypes.txt
==============================================================================
--- (empty file)
+++ pypy/extradoc/planning/roadmap/task_ctypes.txt Fri Dec 14 21:41:34 2007
@@ -0,0 +1,7 @@
+Support app-level ctypes
+========================
+
+As a first approach for providing C-level bindings, we should implement
+the ctypes module on top of already existing _ffi wrapper. This would
+allow to access quite a bit of libraries which use ctypes already
+(like SDL wrapper).
Modified: pypy/extradoc/planning/roadmap/task_wrapper_generator.txt
==============================================================================
--- pypy/extradoc/planning/roadmap/task_wrapper_generator.txt (original)
+++ pypy/extradoc/planning/roadmap/task_wrapper_generator.txt Fri Dec 14 21:41:34 2007
@@ -8,10 +8,4 @@
development, it would be natural to do Swig. Once PyPy gets traction
we expect proponents of other tools to make their own ports.
-In addition to Swig, a PyPy version of ctypes should be implemented.
-An attempt to build a layer on top of the existing ctypes
-implementation for CPython has failed. Ctypes was not written with
-this kind of reuse in mind, and it would be harder to change it
-than to make an RPython implementation from scratch.
-XXX Some example use case needed here.
More information about the Pypy-commit
mailing list