From 935c72a554295cee628c344a3d7352de1f2efa84 Mon Sep 17 00:00:00 2001
From: Marius Vollmer <mvo@zagadka.de>
Date: Mon, 9 Aug 2004 21:53:03 +0000
Subject: [PATCH] Removed caveat of pretty-print using its own 'write'
 implementation.

---
 doc/ref/misc-modules.texi | 19 -------------------
 1 file changed, 19 deletions(-)

diff --git a/doc/ref/misc-modules.texi b/doc/ref/misc-modules.texi
index 6f262701e..2f3173e0a 100644
--- a/doc/ref/misc-modules.texi
+++ b/doc/ref/misc-modules.texi
@@ -36,25 +36,6 @@ Print the textual representation of the Scheme object @var{obj} to
 given.
 @end deffn
 
-Beware: Since @code{pretty-print} uses it's own write procedure, it's
-output will not be the same as for example the output of @code{write}.
-Consider the following example.
-
-@lisp
-(write (lambda (x) x))
-@print{}
-#<procedure #f (x)>
-
-(pretty-print (lambda (x) x))
-@print{}
-#[procedure]
-@end lisp
-
-The reason is that @code{pretty-print} does not know as much about
-Guile's object types as the builtin procedures.  This is particularly
-important for smobs, for which a write procedure can be defined and be
-used by @code{write}, but not by @code{pretty-print}.
-
 
 @page
 @node Formatted Output