[svn:mod_parrot] r242 - mod_parrot/trunk/docs

Author: jhorwitz
Date: Fri Aug 31 18:41:22 2007
New Revision: 242

Modified:
   mod_parrot/trunk/docs/nci.txt

Log:
update docs for new namespaces


Modified: mod_parrot/trunk/docs/nci.txt
==============================================================================
--- mod_parrot/trunk/docs/nci.txt	(original)
+++ mod_parrot/trunk/docs/nci.txt	Fri Aug 31 18:41:22 2007
@@ -17,11 +17,12 @@
 2) If an Apache API function cannot be called through NCI, it should be wrapped
    in a small C function that can be called through NCI.  This function should
    be placed in nci.c and its NCI object should be defined in the Parrot
-   namespace ModParrot::NCI.  The function should be prefixed with mpnci_.
-   The PIR code to load the object should be placed in lib/ModParrot/init.pir.
+   namespace ['_modparrot';'NCI'].  The function should be prefixed with
+   mpnci_.  The PIR code to load the object should be placed in
+   lib/ModParrot/init.pir.
 
 3) mod_parrot functions that should be callable via NCI should be placed in
-   nci.c and defined in the Parrot namespace ModParrot::NCI.  The first
+   nci.c and defined in the Parrot namespace ['_modparrot';'NCI'].  The first
    argument passed to the function should be the Parrot interpreter, which
    Parrot will handle for you if you use the 'J' signature.  Each function
    should be prefixed with mpnci_.  The PIR code to load these objects should
@@ -41,7 +42,7 @@
 6) In order to maintain state between the calling Apache process and the NCI
    function, we use the interpreter object, which we can pass to each NCI
    function via the 'J' signature.  Each interpreter contains a context
-   structure (an UnmanagedStruct PMC) at ModParrot::__context that points
+   structure (an UnmanagedStruct PMC) in ['_modparrot'];__context that points
    to a modparrot_context structure.  Use get_interp_ctx() to fetch this in
    your NCI code.  See mod_parrot.h for details.