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

[email protected] Mon, 10 Nov 2008 09:12:08 -0800 (PST)
Newsgroups perl.cvs.mod_parrot
Message-ID <[email protected]>
Author: jhorwitz
Date: Mon Nov 10 09:12:07 2008
New Revision: 485

Modified:
   mod_parrot/trunk/docs/nci.txt

Log:
update namespaces


Modified: mod_parrot/trunk/docs/nci.txt
==============================================================================
--- mod_parrot/trunk/docs/nci.txt	(original)
+++ mod_parrot/trunk/docs/nci.txt	Mon Nov 10 09:12:07 2008
@@ -17,12 +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
+   namespace ['ModParrot';'NCI'].  The function should be prefixed with
    mpnci_.  The PIR code to load the object should be placed in
    lib/mod_parrot.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