Changes between Version 32 and Version 33 of ModParrotHLLDocs

Timestamp:

12/29/08 16:36:07 (13 years ago)

Author:

jhorwitz

Comment:

--

ModParrotHLLDocs

@@ -84 +84 @@
 Like the constructor subroutines above, HLL modules can provide subroutines to merge two configurations.  This is useful when, for example, a particular configuration setting for a directory should be overridden by a different setting in a subdirectory.  Or perhaps your HLL is maintaining an array of values for a virtual host that should be concatenated with the array defined in the main server.  All of this behavior is performed by the merge subroutines.
 
-If a merge subroutine is not provide, Apache will perform the merge itself by completely overriding the base configuration with the new configuration.  This may or may not be desirable for your particular module.
+If a merge subroutine is not provided, Apache will perform the merge itself by completely overriding the base configuration with the new configuration.  This may or may not be desirable for your particular module.
 
 The server merge subroutine is called {{{server_merge}}}, and the directory merge is handled by {{{dir_merge}}}.  They are passed the "base" configuration and the "new" configuration, and are expected to return a merged configuration.  These subroutines should create a new PMC for the merged configuration rather than reusing the PMC from the "new" configuration.  Parrot passes PMCs by reference, and the code would thus be changing the "new" configuration directly, resulting in unexpected behavior.
@@ -431 +431 @@
 }}}
 
-HINT: If you are registering ALL hooks, use an array with the single value MP_HOOK_ALL, rather than populating the array with every hook constant.
+HINT: If you are registering ALL hooks, use an array with the single value {{{MP_HOOK_ALL}}}, rather than populating the array with every hook constant.
 
 == Miscellany ==