[pypy-svn] r10604 - pypy/dist/pypy/documentation
hpk at codespeak.net
hpk at codespeak.net
Thu Apr 14 12:11:58 CEST 2005
Author: hpk
Date: Thu Apr 14 12:11:58 2005
New Revision: 10604
Removed:
pypy/dist/pypy/documentation/trivialobjspace.txt
Modified:
pypy/dist/pypy/documentation/architecture.txt
pypy/dist/pypy/documentation/coding-style.txt
pypy/dist/pypy/documentation/howtopypy.txt
pypy/dist/pypy/documentation/objspace.txt
pypy/dist/pypy/documentation/testdesign.txt
Log:
remove all occurences of Trivial object space
in the documentation. Start to mention "thunk"
without really explaining it (Armin, do you feel
like adding a nice paragraph to the architecture
document?)
Modified: pypy/dist/pypy/documentation/architecture.txt
==============================================================================
--- pypy/dist/pypy/documentation/architecture.txt (original)
+++ pypy/dist/pypy/documentation/architecture.txt Thu Apr 14 12:11:58 2005
@@ -118,14 +118,9 @@
if-statements (or rather, to be pedantic, to implement the
conditional-branching bytecodes into which if-statements get compiled).
-We currently have four working object spaces which can be plugged into
+We currently have three working object spaces which can be plugged into
the interpreter:
-- The Trivial Object Space, which basically delegates almost all
- operations to the underlying CPython interpreter. It was, and still
- is, used to test our interpreter. Alhough it is not essential, it
- remains useful for testing, and thus it is here to stay.
-
- The Standard Object Space, which is an almost complete implementation
of the various Python objects. This is the main focus of this
document, since the Standard Object Space, together with the
@@ -136,9 +131,9 @@
transformation task through "abstract interpretation", which we will
explain later in this document.
-- the Trace Object Space, which wraps either the trivial or the standard
- object space in order to trace the execution of bytecodes, frames and
- object space operations.
+- the Trace Object Space, which wraps e.g. the standard
+ object space in order to trace the execution of bytecodes,
+ frames and object space operations.
The Standard Object Space
=========================
@@ -332,8 +327,8 @@
Trace Object Space
==================
-A recent addition is the Trace Object space, which wraps a standard or
-trivial object space in order to trace all object space operations,
+A recent addition is the Trace Object space, which wraps a standard
+object space in order to trace all object space operations,
frame creation, deletion and bytecode execution. The ease with which
the Trace Object Space was implemented at the Amsterdam Sprint
underlines the power of the Object Space abstraction. (Of course, the
Modified: pypy/dist/pypy/documentation/coding-style.txt
==============================================================================
--- pypy/dist/pypy/documentation/coding-style.txt (original)
+++ pypy/dist/pypy/documentation/coding-style.txt Thu Apr 14 12:11:58 2005
@@ -38,7 +38,6 @@
- objectspace classes are always spelled "ObjSpace". e.g.
- - TrivialObjSpace
- StdObjSpace
- FlowObjSpace
Modified: pypy/dist/pypy/documentation/howtopypy.txt
==============================================================================
--- pypy/dist/pypy/documentation/howtopypy.txt (original)
+++ pypy/dist/pypy/documentation/howtopypy.txt Thu Apr 14 12:11:58 2005
@@ -322,10 +322,9 @@
``xxxobject.py`` contain respectively the definition of the type and its
(default) implementation.
-* `dist-pypy/pypy/objspace`_ contains a few other object spaces: the trivial one
- (but let's forget about it), the trace_ one, the flow_ one. The latter
- is a relatively short piece of code that builds the control flow graphs
- when the interpreter runs in it.
+* `dist-pypy/pypy/objspace`_ contains a few other object the "thunk" one
+ the trace_ one, the flow_ one. The latter is a relatively short piece of
+ code that builds the control flow graphs when the interpreter runs in it.
* `dist-pypy/pypy/translator`_ contains the code analysis and generation stuff.
Start reading from translator.py_, from which it should be easy to follow
Modified: pypy/dist/pypy/documentation/objspace.txt
==============================================================================
--- pypy/dist/pypy/documentation/objspace.txt (original)
+++ pypy/dist/pypy/documentation/objspace.txt Thu Apr 14 12:11:58 2005
@@ -15,9 +15,8 @@
In PyPy, the three parts are clearly separated and can be replaced independently. I will discuss below the reasons I think it is very useful to have, in particular, the object library be replaced. We call object space such an object library. The standard object space is the object space that works just like Python's, that is, the object space whose black boxes are real Python objects that work as expected. We will call wrapped objects the black boxes of an object space.
-Here are four examples of object spaces:
+Here are three examples of object spaces:
-- TrivialObjectSpace_
- StandardObjectSpace_
- AbstractObjectSpace_
- AnnotateObjectSpace_
@@ -33,7 +32,6 @@
------------
.. _ObjectSpaceInterface: objspaceinterface.html
-.. _TrivialObjectSpace: trivialobjspace.html
.. _StandardObjectSpace: stdobjspace.html
.. _AbstractObjectSpace: abstractobjspace.html
.. _AnnotateObjectSpace: annotateobjspace.html
Modified: pypy/dist/pypy/documentation/testdesign.txt
==============================================================================
--- pypy/dist/pypy/documentation/testdesign.txt (original)
+++ pypy/dist/pypy/documentation/testdesign.txt Thu Apr 14 12:11:58 2005
@@ -15,8 +15,9 @@
Both types of tests need an objectspace they can run with (the interpreter
dispatches operations on objects to an objectspace). If you run a test you
-can usually give the '-o' switch to select an object space. E.g. '-o trivial'
-will select the trivial object space. The default is the "Standard Object Space".
+can usually give the '-o' switch to select an object space. E.g. '-o thunk'
+will select the thunk object space. The default is the "Standard Object Space"
+which aims to implement unmodified Python semantics.
.. _`py.test`: http://codespeak.net/py/current/doc/test.html
@@ -32,13 +33,4 @@
python test_all.py
-which will run all tests against the Standard Object Space. If you want
-to test against the TrivialObjectSpace then issue::
-
- python test_all.py -o trivial
-
-For more switches invoke "python test_all.py -h".
-
-This used to be reversed -- the TrivialObjectSpace was the default, and
-you had to specify the StandardObjectSpace. You may find some documentation
-that has not been changed to reflect the new reality.
+For switches to modify test execution invoke "python test_all.py -h".
Deleted: /pypy/dist/pypy/documentation/trivialobjspace.txt
==============================================================================
--- /pypy/dist/pypy/documentation/trivialobjspace.txt Thu Apr 14 12:11:58 2005
+++ (empty file)
@@ -1,17 +0,0 @@
-=================================
-PyPython Trivial Object Space
-=================================
-
-The easiest way to implement an Object Space is to represent a Python object with itself.
-
-A PyPy interpreter using the Trivial Object Space is an interpreter with its own main loop (written in Python), but this main loop manipulates real Python objects and all operations are done directly on the Python objects. For example, "1" really means "1" and when the interpreter encounters the BINARY_ADD bytecode instructions the TrivialObjectSpace will just add two real Python objects together using Python's "+". The same for lists, dictionaries, classes... We just use Python's own.
-
-Of course you cannot do this if the goal is to write PyPy in such a way that it doesn't rely on a real underlying Python implementation like CPython. Still, it works, and it has its own uses, like testing our interpreter, or even interpreting a different kind of bytecode -- for example, it could probably be used to emulate generators in any Python version. (That would be quite slow, however.)
-
-(This is already done; it is funny to watch "dis.dis" disassembling itself painfully slowly :-) )
-
-See StandardObjectSpace_ for the rest of the story.
-
--------------------------------------------------------------------
-
-.. _StandardObjectSpace: stdobjspace.html
More information about the Pypy-commit
mailing list