summaryrefslogtreecommitdiffstats
path: root/doc/src/qtscript.qdoc
diff options
context:
space:
mode:
authorKent Hansen <khansen@trolltech.com>2009-08-06 10:08:50 (GMT)
committerKent Hansen <khansen@trolltech.com>2009-08-06 10:08:50 (GMT)
commit9429424b52a9c66d6313d3085ef5638f87ee0055 (patch)
tree2ceb85f00301cbc9fab020dd29ce65eec9733494 /doc/src/qtscript.qdoc
parent4614dfe4105bfb6bf6b248a5223650fd370edbb2 (diff)
downloadQt-9429424b52a9c66d6313d3085ef5638f87ee0055.zip
Qt-9429424b52a9c66d6313d3085ef5638f87ee0055.tar.gz
Qt-9429424b52a9c66d6313d3085ef5638f87ee0055.tar.bz2
remove docs that mention QScriptValue::{scope,setScope}()
Those functions are internal and we don't want to support them in the JSC back-end, because they expose too much implementation detail of the old back-end.
Diffstat (limited to 'doc/src/qtscript.qdoc')
-rw-r--r--doc/src/qtscript.qdoc38
1 files changed, 0 insertions, 38 deletions
diff --git a/doc/src/qtscript.qdoc b/doc/src/qtscript.qdoc
index 6b8f639..43dc42f 100644
--- a/doc/src/qtscript.qdoc
+++ b/doc/src/qtscript.qdoc
@@ -1230,44 +1230,6 @@
for it, evaluate the script, and finally restore the old context.
\endlist
- \section2 Nested Functions and the Scope Chain
-
- This is an advanced topic; feel free to skip it.
-
- A nested function can be used to "capture" the execution context in which a
- nested function object is created; this is typically referred to as creating
- a \e closure. When, at some later time, the nested function is invoked, it
- can access the variables that were created when the enclosing function was
- invoked. This can perhaps best be illustrated through a small example:
-
- \snippet doc/src/snippets/code/doc_src_qtscript.qdoc 70
-
- The \c{counter()} function initializes a local variable to zero,
- and returns a nested function. The nested function increments
- the "outer" variable and returns its new value. The variable
- persists over function calls, as shown in the following example:
-
- \snippet doc/src/snippets/code/doc_src_qtscript.qdoc 71
-
- The \c{counter()} function can be implemented as a native function, too
- \mdash or rather, as a pair of native functions: One for the outer and
- one for the inner. The definition of the outer function is as follows:
-
- \snippet doc/src/snippets/code/doc_src_qtscript.qdoc 72
-
- The function creates a local variable and initializes it to zero.
- Then it wraps the inner native function, and sets the scope of
- the resulting function object to be the activation object associated
- with this (the outer) function call. The inner function accesses
- the "outer" activation through the scope of the callee:
-
- \snippet doc/src/snippets/code/doc_src_qtscript.qdoc 73
-
- It is also possible to have a hybrid approach, where the outer function
- is a native function and the inner function is defined by a script:
-
- \snippet doc/src/snippets/code/doc_src_qtscript.qdoc 74
-
\section2 Property Getters and Setters
A script object property can be defined in terms of a getter/setter