From 42560c3e9a5fe60083a75088e9ef672f8af7f486 Mon Sep 17 00:00:00 2001
From: Matthias Benkard <code@mail.matthias.benkard.de>
Date: Mon, 6 Aug 2007 20:48:09 +0200
Subject: Document and export classes and special variables.

darcs-hash:8ad27577c51deee5dbfb55b3520d91297cb97cb1
---
 Lisp/parameters.lisp | 66 +++++++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 65 insertions(+), 1 deletion(-)

(limited to 'Lisp/parameters.lisp')

diff --git a/Lisp/parameters.lisp b/Lisp/parameters.lisp
index 3974b89..e9e3057 100644
--- a/Lisp/parameters.lisp
+++ b/Lisp/parameters.lisp
@@ -5,4 +5,68 @@
 (defvar *skip-retaining*     nil)
 
 (defvar *trace-method-calls* nil
-  "FIXME")
+  "Whether to print trace messages of all Objective C method calls.
+
+## Value Type:
+
+a **generalized boolean**.
+
+
+## Initial Value:
+
+__nil__.
+
+
+## Description:
+
+Sometimes it is useful to find out exactly which message calls are done
+in a piece of code that is executed.  If __*trace-method-calls*__ is
+**true**, Objective CL tries to print trace messages to
+__*terminal-io*__ that can be useful for understanding the behaviour
+both of application code and the internals of Objective CL itself.
+
+If __*trace-method-calls*__ is __nil__ (which is the default), no trace
+messages are printed.
+
+Note that there is currently no way of determining the receivers of
+messages.  As this limitation severely limits the usefulness of the
+trace messages, it is expected to be lifted in a future version of
+Objective CL.
+
+
+## Examples:
+
+\(With __install-reader-syntax__ enabled.)
+
+    (defvar *tmp*)
+    (setq *trace-method-calls* t)
+
+    (setq *tmp* [NSString new])
+    ; Invoking [new].
+
+    (setq *tmp* [NSString string])
+    ; Invoking [string].
+    ; Invoking [retain].
+
+    (setq *tmp* nil)
+    (gc :full t)
+    ; Invoking [release].
+    ; Invoking [release].
+
+    (setq *trace-method-calls* nil)
+
+\(Note that objects created by a call to `new' are not retained, because
+it is the user's (that is, the Objective CL framework's) responsibility
+to release them, while convenience constructors such as `string' return
+objects that have already had `autorelease' called on them and must thus
+be retained not to be garbage-collected prematurely.)
+
+
+## Affected By:
+
+  __*terminal-io*__
+
+
+## See also:
+
+  __invoke__, __invoke-by-name__")
-- 
cgit v1.2.3