stas 2003/02/08 18:05:21
Modified: src/docs/1.0/guide install.pod modules.pod porting.pod
strategy.pod
src/docs/general/os/win32 faq.pod
src/docs/general/perl_reference perl_reference.pod
Log:
correct internal xref links
Revision Changes Path
1.21 +7 -4 modperl-docs/src/docs/1.0/guide/install.pod
Index: install.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/install.pod,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- install.pod 29 Jan 2003 23:44:15 -0000 1.20
+++ install.pod 9 Feb 2003 02:05:19 -0000 1.21
@@ -1203,10 +1203,13 @@
the I<x.x.x> convention, instead of using hardcoded version numbers.
Remember to replace the I<xx> place-holders with the version numbers
of the distributions you are about to use. To find out the latest
-stable version number, visit the components' sites. So if I say
-http://perl.apache.org/dist/mod_perl-1.xx.tar.gz , go to
-http://perl.apache.org/dist/ in order to learn the version number of
-the latest stable release and download the appropriate file.
+stable version number, visit the components' sites. So if the
+instructions say:
+
+ http://perl.apache.org/dist/mod_perl-1.xx.tar.gz
+
+go to http://perl.apache.org/download/ in order to learn the version
+number of the latest stable release and download the appropriate file.
Unless otherwise noted, all the components install themselves into a
default location. When you run C<make install> the installation
1.14 +1 -1 modperl-docs/src/docs/1.0/guide/modules.pod
Index: modules.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/modules.pod,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- modules.pod 3 Dec 2002 14:38:37 -0000 1.13
+++ modules.pod 9 Feb 2003 02:05:19 -0000 1.14
@@ -124,7 +124,7 @@
=head1 Apache::DBI - Initiate a persistent database connection
See L<mod_perl and relational
-Databases|guide::databases/Apache_DBI_Initiate_a_persist>
+Databases|guide::databases/Apache__DBI___Initiate_a_persistent_database_connection>
=head1 Apache::Watchdog::RunAway - Hanging Processes Monitor and Terminator
1.17 +30 -26 modperl-docs/src/docs/1.0/guide/porting.pod
Index: porting.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/porting.pod,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- porting.pod 25 Nov 2002 22:00:33 -0000 1.16
+++ porting.pod 9 Feb 2003 02:05:19 -0000 1.17
@@ -39,12 +39,12 @@
It can be a good idea to tighten up some of your Perl programming
practices, since mod_perl doesn't tolerate sloppy programming.
-This chapter relies on a certain level of Perl knowledge. Please
-read through the L<Perl
Reference|general::perl_reference::perl_reference/Perl_Reference_> chapter and
make sure you
-know the material covered there. This will allow me to concentrate on
-pure mod_perl issues and make them more prominent to the experienced
-Perl programmer, which would otherwise be lost in the sea of Perl
-background notes.
+This chapter relies on a certain level of Perl knowledge. Please read
+through the L<Perl Reference|general::perl_reference::perl_reference>
+chapter and make sure you know the material covered there. This will
+allow me to concentrate on pure mod_perl issues and make them more
+prominent to the experienced Perl programmer, which would otherwise be
+lost in the sea of Perl background notes.
Additional resources:
@@ -136,7 +136,8 @@
opposed to anonymous - subroutine defined inside another subroutine)
that refers to a lexically scoped variable defined outside this nested
subroutine. This effect is explained in L<my() Scoped Variable in
-Nested
Subroutines|general::perl_reference::perl_reference/my_Scoped_Variable_in_Nested_S>.
+Nested
+Subroutines|general::perl_reference::perl_reference/my___Scoped_Variable_in_Nested_Subroutines>.
Do you see a nested named subroutine in my script? I don't! What's
going on? Maybe it's a bug? But wait, maybe the perl interpreter sees
@@ -483,7 +484,8 @@
}
To make sure you don't miss these bugs always test your CGI in
-L<single process
mode|general::control::control/Running_a_Server_in_Single_Process_Mode>.
+L<single process
+mode|general::control::control/Running_a_Server_in_Single_Process_Mode>.
To solve this particular C</o> modifier problem refer to L<Compiled
Regular
Expressions|general::perl_reference::perl_reference/Compiled_Regular_Expressions>.
@@ -498,7 +500,7 @@
=head1 @INC and mod_perl
The basic Perl C<@INC> behaviour is explained in section L<use(), require(),
-do(), %INC and @INC
Explained|general::perl_reference::perl_reference/use_require_do_INC_and>.
+do(), %INC and @INC
Explained|general::perl_reference::perl_reference/use____require____do_____INC_and__INC_Explained>.
When running under mod_perl, once the server is up C<@INC> is frozen
and cannot be updated. The only opportunity to I<temporarily> modify
@@ -1201,7 +1203,7 @@
variables on its first invocation. To do that, you would need to
replace each occurrence of return() and warn() with die(). If you do
that, take a look at the section "L<Redirecting Errors to the Client
-instead of error_log|guide::snippets/Redirecting_Errors_to_the_Client>".
+instead of
error_log|guide::snippets/Redirecting_Errors_to_the_Client_Instead_of_error_log>".
I used the above approach when I had a huge configuration file that
was loaded only at server startup, and another little configuration
@@ -1990,11 +1992,12 @@
But you're throwing performance out the window either way. It's best
not to fork at all if you can avoid it. See the "L<Forking or
Executing subprocesses from
-mod_perl|guide::performance/Forking_and_Executing_Subprocess>" section
-to learn about implications of forking.
+mod_perl|guide::performance/Forking_and_Executing_Subprocesses_from_mod_perl>"
+section to learn about implications of forking.
-Also read about
L<Apache::SubProcess|guide::porting/CGI_to_mod_perl_Porting__mod_perl_Coding_guidelines__>
for
-overridden system() and exec() implementations that work with mod_perl.
+Also read about
+L<Apache::SubProcess|guide::modules/Apache__SubProcess> for overridden
+system() and exec() implementations that work with mod_perl.
=head1 Using format() and write()
@@ -2236,8 +2239,8 @@
from request to request. This means that you must never rely on the
value of the global variable if it wasn't initialized at the beginning
of the request processing. See "L<Variables globally, lexically scoped
-and fully
qualified|general::perl_reference::perl_reference/Variables_Globally_Lexically_Sc>"
for more
-info.
+and fully
+qualified|general::perl_reference::perl_reference/Variables_Globally__Lexically_Scoped_And_Fully_Qualified>"
for more information.
You should avoid using global variables unless it's impossible without
them, because it will make code development harder and you will
@@ -2245,7 +2248,7 @@
they are used. Use my() scoped variables wherever you can.
You should be especially careful with L<Perl Special
-Variables|general::perl_reference::perl_reference/The_Scope_of_the_Special_Perl_Va>
which cannot be
+Variables|general::perl_reference::perl_reference/The_Scope_of_the_Special_Perl_Variables>
which cannot be
lexically scoped. You have to use local() instead.
=head1 Generating correct HTTP Headers
@@ -2550,9 +2553,9 @@
Why can't we use a lexical without hitting the nested subroutine
effect? Because when we've discussed L<Apache::Registry
-secrets|guide::porting/Exposing_Apache_Registry_secret> we have seen that the
-code is wrapped in a C<handler> routine, effectively turning any
-subroutines within the file a script resides in into nested
+secrets|guide::porting/Exposing_Apache__Registry_secrets> we have seen
+that the code is wrapped in a C<handler> routine, effectively turning
+any subroutines within the file a script resides in into nested
subroutines. Hence we are forced to use a global in this situation.
Let's make our smart method more elaborate with respect to the
@@ -2651,7 +2654,7 @@
=back
Make sure you read L<Evil things might happen when using
-PerlFreshRestart|guide::troubleshooting/Evil_things_might_happen_when_us>.
+PerlFreshRestart|guide::troubleshooting/Evil_things_might_happen_when_using_PerlFreshRestart>.
=head1 END blocks
@@ -2685,7 +2688,7 @@
used to emulate plain perl's C<END{}> block behavior.
The last paragraph is very important for handling the case of L<'User
-Pressed the Stop Button'|guide::debug/Handling_the_User_pressed_Stop_>.
+Pressed the Stop
Button'|guide::debug/Handling_the__User_pressed_Stop_button__case>.
If you only want something to run once in the parent on shutdown or
restart you can use C<$r-E<gt>register_cleanup()> in the I<startup.pl>.
@@ -3033,9 +3036,10 @@
=head1 Code has been changed, but it seems the script is running the old code
Files pulled in via C<use> or C<require> statements are not
-automatically reloaded when they change on disk. See L<Reloading Modules
-and Required Files|guide::porting/Reloading_Modules_and_Required_F> for more
-info.
+automatically reloaded when they change on disk. See L<Reloading
+Modules and Required
+Files|guide::porting/Reloading_Modules_and_Required_Files> for more
+information.
=head1 The Script Is Too Dirty, But It Does The Job And I Cannot Afford To
Rewrite It.
@@ -3516,7 +3520,7 @@
better performance, mainly because the internals of many of these Perl
modules are implemented in C, therefore we should get a significant
improvement in speed. The section "L<TMTOWTDI: Convenience and
-Performance|guide::performance/TMTOWTDI_Convenience_and_Habit_>"
+Performance|guide::performance/TMTOWTDI__Convenience_and_Habit_vs__Performance>"
compares the three approaches.
What we are going to do is to replace C<CGI.pm> and C<CGI::Cookie>
1.7 +2 -2 modperl-docs/src/docs/1.0/guide/strategy.pod
Index: strategy.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/strategy.pod,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- strategy.pod 11 May 2002 11:54:44 -0000 1.6
+++ strategy.pod 9 Feb 2003 02:05:19 -0000 1.7
@@ -239,8 +239,8 @@
for you!
For implementation notes, see the "L<One Plain and One mod_perl
-enabled
-Apache
Servers|guide::scenario/One_Plain_and_One_mod_perl_enabled_Apache_Servers>"
+enabled Apache
+Servers|guide::scenario/One_Plain_and_One_mod_perl_enabled_Apache_Servers>"
section in the implementations chapter.
=head2 One Plain Apache and One mod_perl-enabled Apache Servers
1.7 +1 -1 modperl-docs/src/docs/general/os/win32/faq.pod
Index: faq.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/general/os/win32/faq.pod,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- faq.pod 20 Jan 2003 00:20:04 -0000 1.6
+++ faq.pod 9 Feb 2003 02:05:20 -0000 1.7
@@ -166,7 +166,7 @@
See the discussion of configuring
L<Apache::Registry|docs::1.0::guide::config/My_CGI_Perl_Code_Gets_Returned_as_Plain_Text_Instead_of_Being_Executed_by_the_Webserver>;
for mod_perl 2.0, a
L<different
-configuration|docs::2.0::user::compat::compat/The_C_Apache__Registry__Family>
+configuration|docs::2.0::user::compat::compat/C_Apache__Registry___C_Apache__PerlRun__and_Friends>
is required.
=head2 I get a "Save-As" dialogue box when calling a script.
1.2 +6 -5
modperl-docs/src/docs/general/perl_reference/perl_reference.pod
Index: perl_reference.pod
===================================================================
RCS file:
/home/cvs/modperl-docs/src/docs/general/perl_reference/perl_reference.pod,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- perl_reference.pod 31 Jul 2002 14:43:17 -0000 1.1
+++ perl_reference.pod 9 Feb 2003 02:05:20 -0000 1.2
@@ -185,8 +185,9 @@
operator and "here documents" are known to throw off Perl's line
numbering, so the messages reporting warnings and errors can have
incorrect line numbers. (See L<Finding the Line Which Triggered the
-Error or Warning|guide::debug/Finding_the_Line_Which_Triggered> for more
-information).
+Error or
+Warning|guide::debug/Finding_the_Line_Which_Triggered_the_Error_or_Warning>
+for more information).
Getting the trace helps a lot.
@@ -366,7 +367,7 @@
For more information see: L<Using global variables and sharing them
between
-modules/packages|general::perl_reference::perl_reference/Using_Global_Variables_and_Shari>
+modules/packages|general::perl_reference::perl_reference/Using_Global_Variables_and_Sharing_Them_Between_Modules_Packages>
and an article by Mark-Jason Dominus about how Perl handles variables
and namespaces, and the difference between C<use vars()> and C<my()> -
http://www.plover.com/~mjd/perl/FAQs/Namespaces.html .
@@ -858,7 +859,7 @@
First of all there is nothing to worry about, as long as you don't
forget to turn the warnings On. If you do happen to have the
"L<my() Scoped Variable in Nested
-Subroutines|general::perl_reference::perl_reference/my_Scoped_Variable_in_Nested_S>"
+Subroutines|general::perl_reference::perl_reference/my___Scoped_Variable_in_Nested_Subroutines>"
problem, Perl will always alert you.
Given that you have a script that has this problem, what are the ways
@@ -2457,7 +2458,7 @@
overcome this by overriding the core die function. This is slightly
more complex than implementing a C<$SIG{__DIE__}> handler, but is far
less magical, and is the right thing to do, according to the
-L<perl5-porters mailing list|guide::help/Get_help_with_Perl>.
+L<perl5-porters mailing list|docs::offsite::other/Perl>.
Overriding core functions has to be done from an external
package/module. So we're going to add that to our C<My::Exception>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
