[pypy-svn] pypy documentation-cleanup: (lac, cfbolz): remove description of dead feature. the rest of the doc is fine.

[cfbolz]

Author: Carl Friedrich Bolz <cfbolz at gmx.de>
Branch: documentation-cleanup
Changeset: r43558:350a66c6c85a
Date: 2011-04-25 11:53 +0200
http://bitbucket.org/pypy/pypy/changeset/350a66c6c85a/

Log:	(lac, cfbolz): remove description of dead feature. the rest of the
	doc is fine.

diff --git a/pypy/doc/stackless.rst b/pypy/doc/stackless.rst
--- a/pypy/doc/stackless.rst
+++ b/pypy/doc/stackless.rst
@@ -7,10 +7,6 @@
 Introduction
 ================
 
-.. include:: crufty.rst
-
-   .. apparently this still works; needs JIT integration; hasn't been maintained for years
-
 PyPy can expose to its user language features similar to the ones
 present in `Stackless Python`_: **no recursion depth limit**, and the
 ability to write code in a **massively concurrent style**.  It actually
@@ -430,32 +426,6 @@
 These cases are not supported yet.
 
 
-Coroutine Cloning
-+++++++++++++++++
-
-In theory, coroutine pickling is general enough to allow coroutines to
-be *cloned* within a process; i.e. from one suspended coroutine, a copy
-can be made - simply by pickling and immediately unpickling it.  Both
-the original and the copy can then continue execution from the same
-point on.  Cloning gives much of the expressive power of full
-*continuations*.
-
-However, pickling has several problems in practice (besides a relatively
-high overhead).  It is not a completely general solution because not all
-kinds of objects can be pickled; moreover, which objects are pickled by
-value or by reference only depends on the type of the object.  For the
-purpose of cloning, this means that coroutines cannot be
-pickled/unpickled in all situations, and even when they can, the user
-does not have full control over which of the objects currently reachable
-from a coroutine will be duplicated, and which will be shared with the
-original coroutine.
-
-For this reason, we implemented a direct cloning operation.  It has been
-deprecated for some time, however, as it was slightly buggy and relied
-on a specific (and deprecated) garbage collector.  It is not available
-out of the box right now, so we will not talk any more about this.
-
-
 Composability
 +++++++++++++