avoid warnings in diagnostics.pm; pod tweaks (from Peter Prymmer

[p5sagit/p5-mst-13.2.git] / pod / perlxstut.pod

diff --git a/pod/perlxstut.pod b/pod/perlxstut.pod
index 8a96c89..4756a9e 100644 (file)
--- a/pod/perlxstut.pod
+++ b/pod/perlxstut.pod
@@ -24,7 +24,7 @@ them.  If you find something that was missed, please let me know.
 This tutorial assumes that the make program that Perl is configured to
 use is called C<make>.  Instead of running "make" in the examples that
 follow, you may have to substitute whatever make program Perl has been
-configured to use.  Running "perl -V:make" should tell you what it is.
+configured to use.  Running B<perl -V:make> should tell you what it is.
 
 =head2 Version caveat
 
@@ -114,6 +114,7 @@ The file Mytest.pm should start with something like this:
        package Mytest;
 
        use strict;
+        use warnings;
 
        require Exporter;
        require DynaLoader;
@@ -190,7 +191,7 @@ You can safely ignore the line about "prototyping behavior".
 
 If you are on a Win32 system, and the build process fails with linker
 errors for functions in the C library, check if your Perl is configured
-to use PerlCRT (running "perl -V:libc" should show you if this is the
+to use PerlCRT (running B<perl -V:libc> should show you if this is the
 case).  If Perl is configured to use PerlCRT, you have to make sure
 PerlCRT.lib is copied to the same location that msvcrt.lib lives in,
 so that the compiler can find it on its own.  msvcrt.lib is usually
@@ -201,11 +202,11 @@ example only, we'll create our own test script.  Create a file called hello
 that looks like this:
 
        #! /opt/perl5/bin/perl
-       
+
        use ExtUtils::testlib;
-       
+
        use Mytest;
-       
+
        Mytest::hello();
 
 Now we make the script executable (C<chmod -x hello>), run the script
@@ -475,7 +476,7 @@ section on the argument stack.
 In general, it's not a good idea to write extensions that modify their input
 parameters, as in Example 3.  Instead, you should probably return multiple
 values in an array and let the caller handle them (we'll do this in a later
-example).  However, in order to better accomodate calling pre-existing C
+example).  However, in order to better accommodate calling pre-existing C
 routines, which often do modify their input parameters, this behavior is
 tolerated.
 
@@ -504,7 +505,7 @@ Also create a file mylib.c that looks like this:
 
        #include <stdlib.h>
        #include "./mylib.h"
-       
+
        double
        foo(int a, long b, const char *c)
        {
@@ -905,7 +906,7 @@ to assist in making the interface between Perl and your extension simpler
 or easier to understand.  These routines should live in the .pm file.
 Whether they are automatically loaded when the extension itself is loaded
 or only loaded when called depends on where in the .pm file the subroutine
-definition is placed.  You can also consult L<Autoloader> for an alternate
+definition is placed.  You can also consult L<AutoLoader> for an alternate
 way to store and load your extra subroutines.
 
 =head2 Documenting your Extension