comparison docs/src/index.txt @ 85:e9f450d30c0e

Added more documentation.
author Atul Varma <varmaa@toolness.com>
date Sun, 09 Aug 2009 15:37:29 -0700
parents fabd3f2271fa
children e455f0f00e98
comparison
equal deleted inserted replaced
84:10205d88f6ff 85:e9f450d30c0e
94 pymonkey can be really usable. Here's some of them. 94 pymonkey can be really usable. Here's some of them.
95 95
96 **Garbage Collection** 96 **Garbage Collection**
97 97
98 Python's garbage collection uses reference counting, whereas 98 Python's garbage collection uses reference counting, whereas
99 SpiderMonkey's is mark-and-sweep. We'll likely run into situations 99 SpiderMonkey's is mark-and-sweep. It's possible for there to be
100 where there are cycles that exist between SpiderMonkey and Python 100 situations where there are cycles that exist between SpiderMonkey and
101 objects; this is actually quite similar to the relationship between 101 Python objects; this is actually quite similar to the relationship
102 XPCOM and JavaScript in the Mozilla platform--XPCOM uses reference 102 between XPCOM and JavaScript in the Mozilla platform--XPCOM uses
103 counting too--so detecting such cycles will probably involve creating 103 reference counting too--so detecting such cycles will probably involve
104 something akin to `XPCOM's cycle collector 104 creating something akin to `XPCOM's cycle collector
105 <https://developer.mozilla.org/en/Interfacing_with_the_XPCOM_cycle_collector>`_. 105 <https://developer.mozilla.org/en/Interfacing_with_the_XPCOM_cycle_collector>`_.
106
107 For the time being, however, such cycles can be manually broken via
108 :meth:`pymonkey.Context.clear_object_private()` on valid objects and functions.
106 109
107 Indices and Tables 110 Indices and Tables
108 ================== 111 ==================
109 112
110 * :ref:`genindex` 113 * :ref:`genindex`