Add a bunch of autogenerated index entries.

[ibg.git] / chapters / 14.rst

diff --git a/chapters/14.rst b/chapters/14.rst
index aed53b33efdf106c1412dcce9810786fc13d6857..396261f556cfcc55212b9f8cfaf073cbbc2af6ac 100644 (file)
--- a/chapters/14.rst
+++ b/chapters/14.rst
@@ -306,8 +306,13 @@ two-state variables are attributes.
 Properties
 ----------
 
 Properties
 ----------
 

+.. Generated by autoindex
+.. index::
+   pair: before; library property
+   pair: name; library property
+

 The library defines around forty-eight standard property variables (such 
 The library defines around forty-eight standard property variables (such 

-as ``before`` or ``name``), but you can readily create further ones just 
+as :prop:`before` or :prop:`name`), but you can readily create further ones just 

 by using them within an object definition.
 
 You can create and initialise a property in an object's ``with`` segment:
 by using them within an object definition.
 
 You can create and initialise a property in an object's ``with`` segment:


@@ -366,6 +371,9 @@ and are usually called automatically by the library, or manually by::
 
   obj_id.property()                    ! everywhere
 
 
   obj_id.property()                    ! everywhere
 

+.. index::
+   single: arguments (of a routine)
+

 Arguments and local variables
 -----------------------------
 
 Arguments and local variables
 -----------------------------
 


@@ -405,11 +413,15 @@ or implicitly when the routine runs out of statements. If none of these
 
   [ routine_id; statement; statement; ... statement; ];
 
 
   [ routine_id; statement; statement; ... statement; ];
 

-returns ``true`` and ::
+.. Generated by autoindex
+.. index::
+   pair: true; library constant
+
+returns :const:`true` and ::

 
   property [; statement; statement; ... statement; ]
 
 
   property [; statement; statement; ... statement; ]
 

-return ``false``.
+return :const:`false`.

 
 This difference is *important*. Remember it by the letter pairs STEF: 
 left to themselves, Standalone routines return True, Embedded routines 
 
 This difference is *important*. Remember it by the letter pairs STEF: 
 left to themselves, Standalone routines return True, Embedded routines 


@@ -608,7 +620,7 @@ you'll come across.
     if (MyVar) ...
 
   Note that the following statement specifically tests whether ``MyVar`` 
     if (MyVar) ...
 
   Note that the following statement specifically tests whether ``MyVar`` 

-  contains ``true`` (1), *not* whether its value is anything other than 
+  contains :const:`true` (1), *not* whether its value is anything other than 

   zero. ::
 
     if (MyVar == true) ...
   zero. ::
 
     if (MyVar == true) ...


@@ -660,8 +672,13 @@ you'll come across.
 "number" property and "general" attribute
 -----------------------------------------
 
 "number" property and "general" attribute
 -----------------------------------------
 

-The library defines a standard ``number`` property and a standard 
-``general`` attribute, whose roles are undefined: they are 
+.. Generated by autoindex
+.. index::
+   pair: general; library attribute
+   pair: number; library property
+
+The library defines a standard :prop:`number` property and a standard 
+:attr:`general` attribute, whose roles are undefined: they are 

 general-purpose variables available within every object to designers as 
 and when they desire.
 
 general-purpose variables available within every object to designers as 
 and when they desire.
 


@@ -702,13 +719,17 @@ is virtually unlimited.
 Setting up the object tree
 --------------------------
 
 Setting up the object tree
 --------------------------
 

+.. Generated by autoindex
+.. index::
+   pair: found_in; library property
+

 Throughout this guide, we've defined the initial position of each object 
 within the overall object tree either by explicitly mentioning its 
 parent's ``obj_id`` (if any) in the first line of the object definition 
 -- what we've been calling the header information -- or, for a few 
 objects which crop up in more than one place, by using their 
 Throughout this guide, we've defined the initial position of each object 
 within the overall object tree either by explicitly mentioning its 
 parent's ``obj_id`` (if any) in the first line of the object definition 
 -- what we've been calling the header information -- or, for a few 
 objects which crop up in more than one place, by using their 

-``found_in`` properties. For example, in "William Tell" we defined 
-twenty-seven objects; omitting those which used ``found_in`` to define 
+:prop:`found_in` properties. For example, in "William Tell" we defined 
+twenty-seven objects; omitting those which used :prop:`found_in` to define 

 their placement at the start of the game, we're left with object 
 definitions starting like this::
 
 their placement at the start of the game, we're left with object 
 definitions starting like this::