From a1c3f47491b98cd9026f8e853cc9e72630805c12 Mon Sep 17 00:00:00 2001
From: Paul Buetow <paul@buetow.org>
Date: Sun, 26 Oct 2008 12:51:57 +0000
Subject: added the "scope" function

---
 docs/pod/fype.tex | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

(limited to 'docs/pod/fype.tex')

diff --git a/docs/pod/fype.tex b/docs/pod/fype.tex
index 8bdd585..7609a00 100644
--- a/docs/pod/fype.tex
+++ b/docs/pod/fype.tex
@@ -179,7 +179,7 @@ All paranthesis of function calls are optional. They help to make the code bette
 \subsection*{Scopeing\label{Scopeing}\index{Scopeing}}
 
 
-A new scope starts with an \{ and ends with an \}. An exception is a procedure, which does not use its own scope (see later in this manual). Control statements and functions support scopeings. Here is a small example how to use scopes:
+A new scope starts with an \{ and ends with an \}. An exception is a procedure, which does not use its own scope (see later in this manual). Control statements and functions support scopeings.  The \textbf{scope} function will print out all available symbols at the current position. Here is a small example of how to use scopes:
 
 \begin{verbatim}
         my foo = 1;
@@ -194,6 +194,11 @@ A new scope starts with an \{ and ends with an \}. An exception is a procedure,
 \begin{verbatim}
                         # Prints out 1
                         put defined bar;
+\end{verbatim}
+\begin{verbatim}
+                        # Prints out all available symbols at this
+                        # point to stdout. Those are: bar and foo
+                        scope;
                 }
 \end{verbatim}
 \begin{verbatim}
-- 
cgit v1.2.3

