scratch/igc 344038a4241: igc.org: The registry, mention root_create

[Gerd Moellmann]

branch: scratch/igc
commit 344038a4241590ee72b2c09da7533e398222b302
Author: Gerd Möllmann <gerd@gnu.org>
Commit: Gerd Möllmann <gerd@gnu.org>

    igc.org: The registry, mention root_create
---
 admin/igc.org | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/admin/igc.org b/admin/igc.org
index c14b156c13c..bb3fe5ca024 100644
--- a/admin/igc.org
+++ b/admin/igc.org
@@ -144,7 +144,7 @@ objects are therefore never copied, and their address does 
not change.
 * The registry
 
 The MPS shields itself from knowing application details, for example
-which GC roots the application has, which threads, how objects look
+which GC roots an application has, which threads, how objects look
 like and so on. MPS has an internal model instead which describes
 these details.
 
@@ -163,6 +163,15 @@ Igc collects all these MPS handles in a 'struct igc'. This 
"registry"
 of MPS handles is found in the global variable 'global_igc' and thus
 can be accessed from anywhere.
 
+The creation of MPS model objects and their registration are usually
+combined into a functions in igc. For example, the call to create an MPS
+root object, error checking, and putting the root handle into the
+registry is factored out into one function =root_create=. Other functions
+like =root_create_ambig= and =root_create_exact= exist to create different
+kinds of roots. This is just the result of factoring out commonalities
+so that not every caller has to deal with the necessarily complex
+argument list of =root_create=.
+
 * Root scan functions
 
 MPS allows us to specify roots having tailor-made scan functions that