[pypy-svn] r38904 - pypy/dist/pypy/doc

pedronis at codespeak.net pedronis at codespeak.net
Thu Feb 15 15:59:57 CET 2007


Author: pedronis
Date: Thu Feb 15 15:59:56 2007
New Revision: 38904

Modified:
   pypy/dist/pypy/doc/faq.txt
Log:
finish reviewing the faq



Modified: pypy/dist/pypy/doc/faq.txt
==============================================================================
--- pypy/dist/pypy/doc/faq.txt	(original)
+++ pypy/dist/pypy/doc/faq.txt	Thu Feb 15 15:59:56 2007
@@ -269,9 +269,12 @@
 Do I have to rewrite my programs in RPython?
 --------------------------------------------
 
-No.  PyPy always runs your code in its own interpreter, which is a full
-and compliant Python 2.4 interpreter.  RPython_ is only the language in
-which parts of PyPy itself are written.  XXX
+No.  PyPy always runs your code in its own interpreter, which is a
+full and compliant Python 2.4 interpreter.  RPython_ is only the
+language in which parts of PyPy itself are written and extension
+modules for it.  The answer whether something needs to be written as
+an extension module, apart from glueing external libraries, will
+change over time as speed for normal Python code improves.
 
 -------------------------
 Which backends are there?
@@ -302,24 +305,15 @@
 .. _Squeak: translation.html#gensqueak
 .. _`Common Lisp`: translation.html#gencl
 
--------------------------------------------------------
-Are there other projects that need the PyPy tool chain?
--------------------------------------------------------
-
-XXX
-
 ----------------------
 How do I compile PyPy?
 ----------------------
 
-See the `getting-started`_ guide.  Note that at the moment this produces
-an executable that contains a lot of things that are hard-coded for your
-particular system (including paths and other stuff), so it's not
-suitable for being installed or redistributed.    XXX
-
----------------------------------
-How do I compile my own programs?
----------------------------------
+See the `getting-started`_ guide.
+
+--------------------------------------
+How do I compile my own interpreters?
+--------------------------------------
 
 Start from the example of
 `pypy/translator/goal/targetnopstandalone.py`_, which you compile by
@@ -330,35 +324,7 @@
 You can have a look at intermediate C source code, which is (at the
 moment) put in ``/tmp/usession-*/testing_1/testing_1.c``.  Of course,
 all the function and stuff indirectly used by your ``entry_point()``
-function has to be RPython_.     XXX
-
---------------------------------------------
-Why isn't there a simpler way of doing that?
---------------------------------------------
-
-One answer is that "officially speaking" supporting this is not a goal
-of the PyPy project.
-
-XXX
-
-A better answer might be that when the target of compilation turns out
-not to be RPython, working out *why* can be very difficult, and
-working on the annotator to make these messages clearer -- even if
-possible -- would take time away from other development tasks.
-
-It's not that writing RPython is difficult, but if there was some kind
-of rpythonc compiling tool there would be much more temptation to try
-to compile arbitrary, pre-existing Python programs and this is fairly
-unlikely to work (to start, there is very little in the way of an
-"RPython standard library"). XXX outdated
-
-
----------------------------------------------------------------------------
-What does the error message "slice start must be proven non-negative" mean?
----------------------------------------------------------------------------
-
-XXX
-
+function has to be RPython_.
 
 
 .. _`RPython`: coding-guide.html#rpython



More information about the Pypy-commit mailing list