gozer 2004/09/09 16:17:38
Modified: src/docs/2.0/api/ModPerl Util.pod
Log:
it's called unload_package, not unload_module
Revision Changes Path
1.14 +5 -5 modperl-docs/src/docs/2.0/api/ModPerl/Util.pod
Index: Util.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/api/ModPerl/Util.pod,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- Util.pod 9 Sep 2004 22:41:16 -0000 1.13
+++ Util.pod 9 Sep 2004 23:17:38 -0000 1.14
@@ -19,7 +19,7 @@
ModPerl::Util::untaint($string);
# removes a module as best as it can
- ModPerl::Util::unload_module($module);
+ ModPerl::Util::unload_package($module);
@@ -161,12 +161,12 @@
-=head2 C<unload_module>
+=head2 C<unload_package>
Unloads a stash from the current Perl interpreter in the safest way
possible.
- ModPerl::Util::unload_module($stash);
+ ModPerl::Util::unload_package($stash);
=over 4
@@ -190,9 +190,9 @@
This function may wipe off things loaded by other modules, if the
latter have inserted things into the C<$stash> it was told to unload.
-C<unload_module()> takes care not to delete sub-stashes when deleting
+C<unload_package()> takes care not to delete sub-stashes when deleting
the requested stash. So for example if C<CGI> and C<CGI::Carp> are
-loaded, calling C<unload_module('CGI')> won't affect C<CGI::Carp>.
+loaded, calling C<unload_package('CGI')> won't affect C<CGI::Carp>.
If the module's stash had a corresponding XS shared object loaded it
will be unloaded as well.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
