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

cfbolz at codespeak.net cfbolz at codespeak.net
Tue Feb 13 11:57:14 CET 2007


Author: cfbolz
Date: Tue Feb 13 11:57:14 2007
New Revision: 38671

Modified:
   pypy/dist/pypy/doc/faq.txt
Log:
try to answer these two questions


Modified: pypy/dist/pypy/doc/faq.txt
==============================================================================
--- pypy/dist/pypy/doc/faq.txt	(original)
+++ pypy/dist/pypy/doc/faq.txt	Tue Feb 13 11:57:14 2007
@@ -178,17 +178,24 @@
 
 .. _`RPython description`: coding-guide.html#restricted-python
 
---------------------------------------------------------------------
-What do you mean by "being RPython always applies to a full program?
---------------------------------------------------------------------
 
-XXX
-
------------------------------------------
-What does a "NOT_RPYTHON" docstring mean?
------------------------------------------
+--------------------------------------------------------------------------
+What do you mean by "full program"? All the code in all the modules I use?
+--------------------------------------------------------------------------
+
+"Full program" in the context of "being RPython" is all the code reachable from
+an "entry point" function. The translation toolchain follows all calls
+recursively and discovers what belongs to the program and what not.
+
+------------------------------------------------------
+What's the ``"NOT_RPYTHON"`` I see in some docstrings?
+------------------------------------------------------
+
+If you put "NOT_RPYTHON" into the docstring of a function and that function is
+found while trying to translate an RPython program, the translation process
+stops and reports this as an error. You can therefore mark functions as
+"NOT_RPYTHON" to make sure that they are never analyzed.
 
-XXX
 
 -------------------------------------------------------------------
 Couldn't we simply take a Python syntax tree and turn it into Lisp?



More information about the Pypy-commit mailing list